Managing required packages in nALFS
vassilidzuba at nerim.net
Sun Sep 29 13:03:32 PDT 2002
Well, do as you prefer of course...
AFAIK, my patches don't break anything, but i'm not sure they are
"production quality" either.
For instance, I didn't look very carefully at the command interface
so that the patches are activated only by a parameter in the command line,
but cannot be activated when running the application (or, if they
can it's without my knowledge...).
There are a few more patches that i would like to implement (or see somebody implement):
- a conditional execution (with a tag <if>)
- a attribute or subelement of <unpack> that contains the checksum of the archive,
so that we could check its validity befor unpacking
I'll wait for the next version of nALFS before looking at it.
Recently, i have been occupied mostly with writing a BLFS profile (it contains about
100 packages now).
On Sun, 29 Sep 2002 12:35:52 +0000 (UTC)
haski at sezampro.yu (Neven Has) wrote:
> On Sun, Sep 29, 2002 at 01:58:12PM +0200, Neven Has wrote:
> > I was stupid enough to make a lot of changes since 1.0.0 in July and
> > Or, I was thinking if it might be better to just release 1.0.1 sooner
> 1.1.* of course. 8-)
> Unsubscribe: send email to listar at linuxfromscratch.org
> and put 'unsubscribe alfs-discuss' in the subject header of the message
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe alfs-discuss' in the subject header of the message
More information about the alfs-discuss