On 9/4/07, Kevin Williams <[EMAIL PROTECTED]> wrote: > > >It's possible, there was a patch to add paco support to jhalfs that was > >included in a few of the past versions of jhalfs, but it wasn't being > >maintained by the person who created it for a while and was eventually > >removed. > > Yeah ! I read that ! What was discussed was about the xsl files. Which would > require > knowing xls !! I were wondering if I could simply insert a command > somewhere. I guess, > I found a way. It is not so easy and would require editing each of the > scripts and changing > the 'make install' lines. Possibly some scripting using sed can achieve > this. Not sure, > how I could do the same for those packages which, do not include a 'make > install' line and > those which, dynamically create files (convert-mans script which converts > man pages for eg.).
With jhalfs (and the *lfs books) in their current form, simply kludging in the commands in the generated files is probably the easiest way to go right now. Just wrap all the installing commands in paco -lp+ <package> "<commands>". I've been meaning to do something with this for quite some time, but I always get about half an hour into it and then drop it for one reason or another. The problem is that for jhalfs to do anything smart about inserting commands into the XML stream, it needs more attributes about the current commands. Manuel and I have discussed this a few times, and I think there should be some trivial XML additions after both books (LFS and BLFS) go to 6.3. I already have a local patch to add the appropriate attributes to LFS, but BLFS would be a lot more work since there's just a lot of packages there. The next problem is that the jhalfs XSL stylesheets are not particularly modular right now, and the only real way to attack this (IMO) is at the XSL level. Ideally, the XSL would have well defined entry points that would allow another stylesheet to step in and do something differently (XSLT is designed to do this). This is the part where I always get bogged down. I do actually understand the XSL fairly well, but there are a lot of workarounds in jhalfs that make separating the templates more difficult. These guys have to handle a bunch of issues where the book just has the implicit assumption that the user will do the right thing. The final step would be to expose these extra stylesheets in the config so they were used appropriately. Manuel and George have done a very nice job with the configuration, so I'm pretty confident this would come together. But I really think this would all be possible without too much code in jhalfs. A lot of the work would have to come at the book level so that jhalfs would receive more information about the commands in the book and what they're for. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/alfs-discuss FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
