|
|
@@ -25,7 +25,7 @@
|
|
|
available in order to run the test suites. The third list of dependencies are
|
|
|
packages that require this package to be built and installed in its final
|
|
|
location before they are built and installed. In most cases, this is because
|
|
|
- these packages will hardcode paths to binaries within their scripts. If not
|
|
|
+ these packages will hard code paths to binaries within their scripts. If not
|
|
|
built in a certain order, this could result in paths of /tools/bin/[binary]
|
|
|
being placed inside scripts installed to the final system. This is obviously
|
|
|
not desirable.</para>
|
|
|
@@ -33,9 +33,9 @@
|
|
|
<para>The last list of dependencies are optional packages that are not
|
|
|
addressed in LFS, but could be useful to the user. These packages may have
|
|
|
additional mandatory or optional dependencies of their own. For these
|
|
|
- dependencies, the recommeded practice is to install them after completion of
|
|
|
+ dependencies, the recommended practice is to install them after completion of
|
|
|
the LFS book and then go back an rebuild the LFS package. In several cases,
|
|
|
- reinstallation is addressed in BLFS.</para>
|
|
|
+ re-installation is addressed in BLFS.</para>
|
|
|
|
|
|
<!-- Begin Acl dependency info -->
|
|
|
<bridgehead renderas="sect2" id="acl-dep">acl</bridgehead>
|
Bruce Dubbs