Date: Sun, 21 Jul 1996 18:48:30 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: DJ Delorie <dj AT delorie DOT com>
Cc: djgpp-workers AT delorie DOT com
Subject: Re: Long filenames in zip files (was: snapshot 960720)
In-Reply-To: <199607211305.JAA28171@delorie.com>
Message-Id: <Pine.SUN.3.91.960721164133.6686A-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Sun, 21 Jul 1996, DJ Delorie wrote:

> I build the zips under dos, or under linux from a dos 8.3 filesystem.
> Aside from fixing up the makefiles etc to expect 8.3 truncated names,
> there's not much I can do to lfn the zip files.

Well, I've found this to be simpler than it seems.  I also build the zips
under native MSDOS, with no LFN support whatsoever.  However, Zip 2.01
will actually record the original long filename in the exact lettercase as
you submit it.  There are only two problems with this approach: 

	- you cannot use wildcards or just the directory names, you need to
feed Zip with the full list of the filenames;
	- filenames that are illegal on MSDOS cannot be used.

The first problem is taken care of if you use a response file.  I prepare
the response file by editing the contents of the original .tar.gz
distribution as listed by DJTAR, then add DJGPP-specific files (which are
usually just a few). 

The second problem doesn't have any solution, because I know of no unzip 
program that can rename the illegal names in the same way DJTAR does, and 
Zip won't allow you to put such names in the archive anyway.

So I suggest to put the long filenames into the zips, and leave the 
illegal names in their DOS format (people who use Win95 will have to 
rename them manually).  This should take us a large step towards being 
LFN-clean (IMHO).