Patch for nALFS

Jason Gurtz jason at
Tue Dec 18 13:54:44 PST 2001

> > Neven Has <haski at sezampro.yu> wrote:
> > Locations with type="remote" could be handled differently.
> > Files could be stored in some default (and configurable)
> > directory and connection problems could be also handled nicely.
> Agreed.  A top level "meta type" element, or a processing
> instruction to hold
> that kind of parser config data (the download storeage location etc.)?
> > I also like putting all that "meta" information in the
> > element of it's own.  I always get a funny feeling after
> > adding even <version> and <name> on the same depth level as
> > <build> and friends. It doesn't seem natural to me. This is
> > something that Felipe is also suggesting - separating all that
> > info from the building instructions (maybe not by using
> > <meta>, we might need something more descriptive) could be nice.


> > But this would be a big syntax change again, because it's
> > incompatible with current profiles. And adding
> > is_new_new_syntax() (god forbid ;) or is_syntax_version(3)
> > would make me (and probably Mark) very unhappy. ;)
> Yes.  Hmmmm! mmm?  Could we not begin to think in a more
> eXtensible way?

Yes, all of the above seems like good paths to aim for.

> As for the profile users, I can provide a style sheet to do
> the job of transformation (this one would be much easier), as
> a CGI on my server, (just backticking till I learn the JAXP
> and Java serlet foo.)  Given a database of download URLs and
> package info, (possibly like freshmeat's) I could even
> generate the required info for at least aome of the packages.
> The LFS base profiles could import the info from the book XML.

Maybe by working with Gerard, Ian, and or HIghoS these things can be put
on the LFS site?

> [...] have failed to learn enough, C++ or find suitable C++ XML
> APIs on Linux to learn enough to help out.

I thought of the IBM C++ XML API off the top of my head and I've heard
of @ least 2 or 3 others from here and there.




Unsubscribe: send email to listar at
and put 'unsubscribe alfs-discuss' in the subject header of the message

More information about the alfs-discuss mailing list