On 10/17/06, Alan Lord <[EMAIL PROTECTED]> wrote:
Dan Nicholson wrote:
...
> What I'm proposing is that there is a generic pm.xsl that is initially
> empty. I.e., in the default case, nothing happens. You can fill in the
> details yourself. Ideally, only this one file would need to be edited
> to add support for <your package manager>.
>
I hope I'm not out-of-line [contributing] here but, personally, I'd like
to see jhalfs (or it's sibling?) develop so it has an architecture that
supports a "plugin" facility. The idea being that anyone can develop new
or innovative features without having to change the base code which
builds THE BOOK. I'm sure something could be done, even in bash, to
allow this sort of flexibility?
This is actually the crux of the problem. If the plugin system could
be written in bash, it would have been done already as both Manuel and
George write excellent shell code. Take a look at the paco patch. It
has to hack up the xsl extraction script, jhalfs functions and LFS
master script to get it to work.
The way it looks presently, the XSL extraction has to be more flexible
somehow to allow a plugin system. Maybe I'm wrong, but it sure seems
like everything else is working around the fact that it's difficult to
extract the commands in a generic way. Unfortunately, the extraction
is done using XSL, and only Manuel really knows XSL. So, it's already
game over by the time you get to the bash level unless you directly
hack up jhalfs like the paco patch does.
--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
