El Sábado, 28 de Mayo de 2005 07:46, Archaic escribió: > I would rather see a link in the book referring to the blfs pages as I > don't think we should be catering to such odd harware configurations. > That is no different than writing the book with the explicit goal of > being able to fully do a remote build with no changes to what the book > lists.
Like Jim said, we don't have now an unique LFS book, but several LFS books, one for each arch, that shares several base info from common XML source files (package description, dependencies, contents, etc..). Each book has their own characteristics based on the target arch: different patches and build commands in some cases, but also different packages version or addition/removal of some packages when needed by the target arch typology. And like Jim said also, I have in mind to find a way to include those BLFS packages needed only for few archs directly from the BLFS sources (except actual build commands, if they must to be different). That is one of the reasons wy I'm trying to unifiy the tagging used on both projects, to can have the same look on imported files. That cuold be usefful also for HLFS, where we actually have several BLFS packages ;-) -- Manuel Canales Esparcia Usuario de LFS nº2886: http://www.linuxfromscratch.org LFS en castellano: http://www.escomposlinux.org/lfs-es http://www.lfs-es.com TLDP-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
