More metadata in LFS xml

On 9/21/07, M.Canales.es <macanamacana-es.com> wrote:
> El Jueves, 19 de Julio de 2007 20:53, Dan Nicholson
escribió:
>
> > My goal is to resurrect the paco
> > functionality, but to do it in a clean way. I.e.,
no patches. In my
> > mind, the only way to do this is at the xsl level.
In the process, I
> > hope to make jhalfs a little more pluggable. We'll
see how that goes.
>
> Dan, can you review the LFS/lfs.xsl code found on the
experimental branch and
> tell me if that is what you was searching for?

Yeah, that's awesome. A lot more call-template instead of
one long
serial template. I haven't looked in detail, but all the
hooks and
entry points means you can make a custom stylesheet with
minimal copy
and paste.

I don't know if it's worth it, but it might be nice to split
out the
hacks into separate templates, too. Then, if you need to
provide a
custom "default" mode userinput template, you
don't have to copy all
the hacks. Just make sure you call the
"default-hacks" template. Just
a thought.

> I'm planning a few other XML changes before start
editing the bash code to
> handle the new build scripts naming schema and content,
but the templates
> structure is ready.

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.

--
Dan
-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discu
ss
FAQ: http://www.linux
fromscratch.org/faq/
Unsubscribe: See the above information page

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.linuxfroms
cratch.org
LFS en castellano: http://www.escomp
oslinux.org/lfs-es http://www.lfs-es.info
TLDP-ES:                           http://es.tldp.org
-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discu
ss
FAQ: http://www.linux
fromscratch.org/faq/
Unsubscribe: See the above information page

El Sábado, 22 de Septiembre de 2007 11:57, M.Canales.es
escribió:

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

And done.

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


Done also. There is now a lot of entry point hocks allowing
full 
customization. But more can be added if needed.


Next step is try to move some on the commands run by the
Makefile to inside 
the scripts.

-- 
Manuel Canales Esparcia
Usuario de LFS nº2886:       http://www.linuxfroms
cratch.org
LFS en castellano: http://www.escomp
oslinux.org/lfs-es http://www.lfs-es.info
TLDP-ES:                           http://es.tldp.org
-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discu
ss
FAQ: http://www.linux
fromscratch.org/faq/
Unsubscribe: See the above information page

El Sábado, 22 de Septiembre de 2007 11:57, M.Canales.es
escribió:

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

Done, plus other fixes to can keep accurate disk usage and
SBU reports.

I think that the XSL redo is finished, except maybe few
changes to made some 
templates more book-agnostic in the aim of can reuse they
for other *LFS 
books.

George, could you look at the generated script to see if I
overlooked 
something?

That new scripts will allow to simplify a lot the Makefile
generation code. 

-- 
Manuel Canales Esparcia
Usuario de LFS nº2886:       http://www.linuxfroms
cratch.org
LFS en castellano: http://www.escomp
oslinux.org/lfs-es http://www.lfs-es.info
TLDP-ES:                           http://es.tldp.org
-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discu
ss
FAQ: http://www.linux
fromscratch.org/faq/
Unsubscribe: See the above information page