Mail Archives: djgpp/1997/02/10/14:37:04
From: | Andy Eskilsson <x-aes AT telelogic DOT se>
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | gzip and long filenames..
|
Date: | 10 Feb 1997 13:33:47 +0100
|
Organization: | Telelogic AB, Sweden
|
Lines: | 24
|
Sender: | x-aes AT ping
|
Message-ID: | <kslo8wc02c.fsf@telelogic.se>
|
Reply-To: | x-aes AT telelogic DOT se
|
NNTP-Posting-Host: | ping.telelogic.se
|
Mime-Version: | 1.0 (generated by tm-edit 7.101)
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Hi!
I was messing around with gzip (gzp124b.zip), and got a bit mad
because of the way it handled long filenames..
Doing gzip on a file "longfilename.longext", resulted in
"longfilename.longegz" and unpacking it I got a file
"longfilename.longe".
It would be nice to have long filenames working OK under win95..
Looking at the gzip sources showed that the magic stuff lied in the
tailor.h file, in definitions of NO_MULTIPLE_DOTS, MAX_EXT_CHARS..
Unfortunetaly it doesn't seem as a good solution to just change these
definitions, but if it is possible to detect if long filenames is
supported during runtime, it could probably be possible to add some
small code to do this and choose the apropriate method of naming?
Duuh shortly, I believe it is a bug that the gzip in the distribution
doesn't support long filenames properly, guess it is FSF's issue, but
until then, solutions?
/Andy
- Raw text -