Changeset c7c32a3 for README.BLFS


Ignore:
Timestamp:
03/19/2017 09:08:18 PM (7 years ago)
Author:
Pierre Labastie <pierre@…>
Branches:
2.4, ablfs-more, legacy, trunk
Children:
a03bccc, c6c2d89
Parents:
9da16d9
Message:

Update READMEs

File:
1 edited

Legend:

Unmodified
Added
Removed

  • README.BLFS

    r9da16d9 rc7c32a3  
    101101    3.2.2 Install to an already running LFS/BLFS system
    102102       If you forgot to install the tools when building xLFS, or want to try
    103     the tools, you can just run the install-blfs-tools.sh script. It will
    104     create the above hierarchy in your home directory and initialize the
    105     tracking file. You have first to make sure that the tracking dir exists
    106     and is writable by the user. You may also populate it with (empty) files
    107     whose names are of the form package-version, for installed packages, so
    108     that they are included into the tracking file.
     103    the tools, you can select the BLFS book from the jhalfs menu. It will
     104    run a script, which creates the above hierarchy in your home directory and
     105    initialize the tracking file. You have first to make sure that the tracking
     106    dir exists and is writable by the user. You may also populate it with
     107    (empty) files whose names are of the form package-version, for installed
     108    packages, so that they are included into the tracking file.
     109
    109110    3.3.3 Working files
    110111        Several files are generated during the process:
    … …  
    162163    chain is generated. Each dependency appears with its priority (required,
    163164    recommended, optional, or external), and it's level. There is a root level
    164     0. The selected packages have level 1. The dependencies of selected packages
    165     have level 2, the dependencies of the dependencies have level 3, and so on.
     165    1. The selected packages have level 2. The dependencies of selected packages
     166    have level 3, the dependencies of the dependencies have level 4, and so on.
    166167    When circular dependencies are found, they appear with a priority of
    167168    "circular". This means that two (or more) dependency chains arrive at the
Note: See TracChangeset for help on using the changeset viewer.