El Sábado, 22 de Septiembre de 2007 00:30, Dan Nicholson escribió:
> Cool. I'm glad you did this. Here's a feature I'd like to see, and the > XSL/Makefile foo has always boggled me a bit. For paco integration, > I'd need to be able to insert another scriptlet at a defined point (at > the end of Ch. 5 and 6). It's easy enough to put the commands into an > <xsl:text> element, but how would it be inserted so that the proper > order was maintained? > > It looks like I'd have to override the "chapter" template to insert > calls to the "paco*" templates. Actually, this looks _much_ easier > with your redo. Yes, a hock to can insert user-made scripts at any desired point is needed if we want customizations centralized at the XSL level. That maybe could replace also the current CUSTOM_TOOLS and BLFS_TOOL support implementations. I must to figure out the best entry point(s) and how to set-up the user scripts numeration. That might implies that the packages must be unpacked from inside the scripts, to made the master.sh code agnostic about if a target will build a package or not. Also, the userinput logic need some change to take care of the fact that commands inside "configuration" sections and several of the ones in non package pages (i.e., userinput commands without a @remap attribute) are actually "install" commands. Plus, I would to share the core templates among all *LFS books (except maybe BLFS due its particularirties), if possible. But that can't be done until have that books migrated also to the new tagging, that will not be made until after having an usable LFS framework. -- 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.info TLDP-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/alfs-discuss FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
