From: "Colin W. Glenn" <cwg01 AT gnofn DOT org>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Upgrading DJGPP installations
Date: Sat, 25 Jan 1997 19:42:26 -0600
Organization: Greater New Orleans Free-Net
Lines: 16
Message-ID: <Pine.GSO.3.95.970125193826.21629F-100000@sparkie.gnofn.org>
References: <Pine DOT LNX DOT 3 DOT 95 DOT 970122145747 DOT 311A-100000 AT capslock DOT com> <32E753A2 DOT 7AB4 AT Mathematik DOT tu-chemnitz DOT de> <Pine DOT GSO DOT 3 DOT 95 DOT 970124221642 DOT 16952C-100000 AT sparkie DOT gnofn DOT org> <32E9E01B DOT 55E3 AT cs DOT com>
NNTP-Posting-Host: sparkie.gnofn.org
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <32E9E01B.55E3@cs.com>
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

On Sat, 25 Jan 1997, John M. Aldrich wrote:
> Colin W. Glenn wrote:
> > Is that the only reason those spacewasters are sitting there taking up
> 
> Absolutely.  On the other hand, I sometimes find the manifest directory
> useful for looking up what package a given file resides in.  This is
> especially useful considering the work I'm doing on DJVERIFY at the
> moment.  :)

I think I'll try door #3, I'll TAR em in an uncompressed archive, that
will give me the means to extract them if I need the individual files, or
view them 'as is' in the TAR.  Also, you might want to add a check the
DJVERIFY to notify the user that they're missing and where might they be
located?  Perhaps build in support for they're being either Zipped or
Tarred or whatevered.  (except deleted, of course. ;)