- 08/26/2022 03:52:18 PM (9 months ago)
- 11.2, 11.3, 11.3-rc1, bdubbs/gcc13, multilib, trunk, xry111/arm64, xry111/clfs-ng, xry111/glibc-2.37, xry111/kcfg-revise, xry111/pip3, xry111/rust-wip-20221008
- b92cf89, cfaf727
- Xi Ruoyao <xry111@…> (08/26/2022 11:35:47 AM)
- Xi Ruoyao <xry111@…> (08/26/2022 03:52:18 PM)
- 1 edited
r5353a19 rbf6f9e7 103 103 of this recommendation is for avoiding a conflict with the system 104 104 package manager (<command>dpkg</command> for example), but LFS does not 105 have a system-wide package manager so this is not a problem. If desired, 106 suppress this warning by running the following commands:</para> 105 have a system-wide package manager so this is not a problem. And, 106 <command>pip3</command> will attempt to check for a new version of 107 itself whenever it's run. As domain name resolving is not configured 108 yet in LFS chroot environment, it will fail to check for a new version 109 and produce a warning. Once we boot the LFS system and set up network 110 connection, it will then produce a warning telling the user to update it 111 from a pre-built wheel on PyPI if any new version is available. But LFS 112 consider <command>pip3</command> a part of Python 3 so it should not be 113 updated separately, and an update from a pre-built wheel will deviate 114 from our purpose to build a Linux system from source code. So the 115 warning for a new <command>pip3</command> version should be ignored as 116 well. If desired, suppress these warnings by running the following 117 commands:</para> 107 118 108 119 <screen><userinput remap="install">cat > /etc/pip.conf << EOF 109 120 [global] 110 121 root-user-action = ignore 122 111 123 EOF 112 124 </userinput></screen>
Note: See TracChangeset for help on using the changeset viewer.