My personal wishlist for nALFS

James Robertson jwrober at
Mon Oct 20 18:21:00 PDT 2003

Neven Has wrote:
> On Fri, Oct 17, 2003 at 01:48:51PM -0600, Gerard Beekmans wrote:
>>On Fri, 2003-10-17 at 09:58, Neven Has wrote:
>>>about files would be lost that way.  And keeping both would be too
>>>ugly, especially because I want to allow editing the list of files
>>>directly from the program (by calling external editor) so the user
>>>can check it out before calling rm on it.
>>I'd put one file per line. If you really need the extra info, code a
>>routine that queries the files' info on a per-demand basis. In shell
>>speak "for file in $(cat logfile); do ls -l $file; done"
> Actually I was thinking about the information obtained using
> "two-finds search".  That method stores the information about
> overwritten files too, which can be useful sometimes.
> Though I'm not sure if all that is worth the trouble...
If we are going to do this, can we also incorporate functionality to 
watch the <requires> element to catch prereqs?

James Robertson -- jwrober at linuxfromscratch dot org
Reg. Linux User -- #160424 --
Reg. LFS User   -- #6981   --
LFS Bugzilla Maintainer    -- http://{blfs-}

More information about the alfs-discuss mailing list