Changes between Initial Version and Version 10 of Ticket #26


Ignore:
Timestamp:
May 10, 2006, 12:52:34 PM (16 years ago)
Author:
chris@…
Comment:

I've just updated the dependency info for all archs and put it all into the Appendix, removed the dependency info from the individual package pages, and reordered all the temp-system sections. Here's what it looks like so far - http://linuxfromscratch.org/~chris/cross-lfs-book/. The only thing left to do is reorder the final-system packages and double-check dependencies for a few more packages (for any arch-specific package that wasn't checked so far, I just copied what was already listed in the book and put it into the Appendix). I think the final-system packages should be ordered the same as in LFS, with the exception of putting arch-specific packages and bootloaders last - does this sound like a good idea?

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #26

    • Property Owner changed from clfs-commits@… to chris
    • Property Milestone changed from to CLFS 1.0
  • Ticket #26 – Description

    initial v10  
    1 LFS just rearranged the build order and added dependency information to a new appendix. The same should be done with CLFS. Most of the info should be the same, since most of the same packages are used, but there are likely to be some issues with CLFS, particularly with arch-specific packages. I would like to do the same as LFS - removing package dependency info from individual package installation pages and putting it all into a single Appendix. One possibility is to do the same thing as with the Materials (Packages and Patches) - have one page that's common to every system, then a second page with arch-specific stuff. Any one else have any thoughts on this?
     1LFS just rearranged the build order and added dependency information to a new appendix. The same should be done with CLFS. Most of the info should be the same, since most of the same packages are used, but there are likely to be some issues with CLFS, particularly with arch-specific packages. I would like to do the same as LFS - removing package dependency info from individual package installation pages and putting it all into a single Appendix. One possibility is to do the same thing as with the Materials (Packages and Patches) - have one page that's common to every system, then a second page with arch-specific stuff. Any one else have any thoughts on this? Also, I need dependency info checked for mips and alpha packages.