Changeset 19abef31 for appendixc


Ignore:
Timestamp:
04/18/2006 06:27:15 PM (18 years ago)
Author:
Jeremy Huntwork <jhuntwork@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 12.2, 12.2-rc1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
d12ae76
Parents:
72d7e28
Message:

Fixed a typo and reversed perspective of explanation in appendix C.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@7537 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:
1 edited

Legend:

Unmodified
Added
Removed
  • appendixc/dependencies.xml

    r72d7e28 r19abef31  
    1616  in circular dependencies, that is, the first package depends on the second
    1717  which in turn depends on the first. Because of these dependencies, the
    18   order in which packages are built in LFS is very important. This purpose
     18  order in which packages are built in LFS is very important. The purpose
    1919  of this page is to document the dependencies of each package built in LFS.</para>
    2020
     
    2323  and install the package in question. The second lists what packages in
    2424  addition to the first list need to be available in order to run the
    25   testsuites. The last list of dependencies are packages that need to be built
    26   and installed in their final location before the package in question. In most
    27   cases, this is because the package in question will hardcode paths to other
    28   binaries within scripts that it installs. If not built in a certain order,
    29   this could result in paths of /tools/bin/[binary] being placed inside scripts
    30   installed to the final system. This is obviously not desirable.</para>
     25  testsuites. The last list of dependencies are packages that require this
     26  package to be built and installed in its final location before they are built
     27  and installed. In most cases, this is because these packages will hardcode
     28  paths to binaries within their scripts. If not built in a certain order,
     29  this could result in paths of /tools/bin/[binary] being placed inside
     30  scripts installed to the final system. This is obviously not desirable.
     31  </para>
    3132
    3233<!-- Begin Autoconf dependency info -->
Note: See TracChangeset for help on using the changeset viewer.