Changeset 7546d8b for chapter08/pkgmgt.xml
- Timestamp:
- 11/21/2023 12:45:26 AM (11 months ago)
- Branches:
- xry111/clfs-ng
- Children:
- e49e2ea
- Parents:
- 2df066c9 (diff), 01247ac (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the(diff)
links above to see all the changes relative to each parent. - File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter08/pkgmgt.xml
r2df066c9 r7546d8b 68 68 all the packages in their dependency order, we do not recommend 69 69 it. </para> 70 </listitem> 71 72 <listitem> 73 <para>Reinstalling the same version of Glibc (&glibc-version; for 74 this release of LFS) with patches should be safe when these patches 75 do not change ABI and API. When a security vulnerability is found 76 in Glibc, we often need to apply such a patch to fix the 77 vulnerability and reinstall Glibc. Consult 78 <ulink url='&lfs-root;lfs/advisories/'>LFS security 79 advisories</ulink> if you are alerted for a published Glibc security 80 vulnerability but unsure about the action to take.</para> 70 81 </listitem> 71 82 … … 153 164 implemented this, and most packages use that command to install binary files and 154 165 libraries. This means that you won't be troubled by this issue most of the time. 155 However, the install process of some packages (notably Mozilla JS166 However, the install process of some packages (notably SpiderMonkey 156 167 in BLFS) just overwrites the file if it exists; this causes a crash. So 157 168 it's safer to save your work and close unneeded running processes … … 186 197 special program to manage the packages. Each package is installed in a 187 198 separate directory. For example, package foo-1.1 is installed in 188 <filename class='directory'>/ usr/pkg/foo-1.1</filename>189 and a symlink is made from <filename>/ usr/pkg/foo</filename> to190 <filename class='directory'>/ usr/pkg/foo-1.1</filename>. When199 <filename class='directory'>/opt/foo-1.1</filename> 200 and a symlink is made from <filename>/opt/foo</filename> to 201 <filename class='directory'>/opt/foo-1.1</filename>. When 191 202 a new version foo-1.2 comes along, it is installed in 192 <filename class='directory'>/ usr/pkg/foo-1.2</filename> and the previous203 <filename class='directory'>/opt/foo-1.2</filename> and the previous 193 204 symlink is replaced by a symlink to the new version.</para> 194 205 195 206 <para>Environment variables such as <envar>PATH</envar>, 196 <envar>LD_LIBRARY_PATH</envar>, <envar>MANPATH</envar>, 197 <envar>INFOPATH</envar> and <envar>CPPFLAGS</envar> need to be expanded to 198 include <filename>/usr/pkg/foo</filename>. If you install more than a few packages, 199 this scheme becomes unmanageable.</para> 200 207 <envar>MANPATH</envar>, <envar>INFOPATH</envar>, 208 <envar>PKG_CONFIG_PATH</envar>, <envar>CPPFLAGS</envar>, 209 <envar>LDFLAGS</envar>, and the configuration file 210 <filename>/etc/ld.so.conf</filename> may need to be expanded to 211 include the corresponding subdirectories in 212 <filename class='directory'>/opt/foo-x.y</filename>.</para> 213 214 <para> 215 This scheme is used by the BLFS book to install some very large 216 packages to make it easier to upgrade them. If you install more 217 than a few packages, this scheme becomes unmanageable. And some 218 packages (for example Linux API headers and Glibc) may not work well 219 with this scheme. 220 <emphasis role='bold'>Never use this scheme system-wide.</emphasis> 221 </para> 201 222 </sect3> 202 223
Note:
See TracChangeset
for help on using the changeset viewer.