El Sábado, 1 de Octubre de 2005 21:03, Jim Gifford escribió:
> Manuel and LFS-dev,
>
>     I have been thinking about this for a few days. Cross-LFS has two
> different options in it, boot and chroot. Boot is a complete reboot and
> chroot is like the standard LFS book. Talking with various people, an
> idea popped into my mind. Having two separate books, Cross-LFS with the
> cross-tools and boot section and a version of the old Multi-Arch LFS
> book which would have the cross-tools section remove and utilizing the
> chroot section.

I think that do you meant a repository setting like this:

BOOK
 top level files (entities, book's index, Makefiles, etc..)
 editor-tools
 stylesheets
 cross-build
  introduction
  final-preps
  cross-tools
  temp-system  (with boot files included)
  temp-tools
 native-build
  introduction (chapter01 from LFS with multi-arch support)
  final-preps (chapter04 from LFS with multi-arch support)
  temp-system (chapter05 from LFS with multi-arch support)
  chroot
 common
  prologue
  partitioning
  materials
  final-system
  bootscripts
  bootable
  the-end
  appendices
  
> The only downfall I see of this idea, is the book rendering issues. Is
> it possible just to render the complete book as it is now, and then make
> new index pages with the sections listed as above?

Yes, you can create all the *-index.xml files that you want rearrangin the 
included files in any way (except placing duplicated ones, of course ;-))

> What type of modifications would we need to do accomplish this?

Appart the repository reestructuration, maybe some changes in the Makefile.

> Would LFS benefit from this? (I say yes)

I say yes also, but only if the multi-archs books replace the current LFS 
book.


-- 
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

Reply via email to