Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <17B78BDF120BD411B70100500422FC6309E337@IIS000>
From: Bernard Dautrevaux <Dautrevaux AT microprocess DOT com>
To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: RE: press for cygwin
Date: Mon, 3 Sep 2001 17:53:02 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"

> -----Original Message-----
> From: Christopher Faylor [mailto:cgf AT redhat DOT com]
> Sent: Monday, September 03, 2001 5:15 PM
> To: cygwin AT cygwin DOT com
> Subject: Re: press for cygwin
> 
> 
> On Mon, Sep 03, 2001 at 10:56:18AM -0400, Charles Wilson wrote:
> >Bernard Dautrevaux wrote:
> >>Why not then just generate files named ".cgw" instead of ".tar.bz2",
> >>and let cygwin setup.exe know that?  Then WinZip will most 
> surely *not*
> >>be able to naturally open these files (neither now or in the future)
> >>and this whole discussion will be closed, as well as any 
> WinZip-related
> >>thread.
> >>
> >>Note that not all packages should use the new suffix; only essential
> >>ones (like cygwin itself) so that the burden on package developers
> >>would not be too bad: after all, once you've installed the 
> basic cygwin
> >>parts using setup.exe, I doubt you will go back to WinZip! :-)
> >
> >Somebody else mentioned this earlier -- and explained that Debian did
> >exactly that.  ".deb" files are just ar archives, but .deb 
> implies that
> >they obey some sort of internal format standard ("CYGWIN-PATCHES" ?
> >/etc/postinstall?  )
> >
> >I actually think this is a pretty good idea.
> 
> It does have merits except for the fact that you lose the ability to
> distinguish between a .gz and .bz2 compressed archive.  setup.exe
> determines the uncompression method from the name.  If it 
> sees .bz2 file
> it says "Bwhaha, this is a WinZip confuser archive.  I will uncompress
> this file with great vigor".  If it sees a .gz file." it thinks "Oh
> well.  I'll uncompress this but I'm not happy about it since 
> the file is
> recognizable to the evil GUI WinZip."
> 
> It's probably possible to add magic number detection to setup.exe to
> circumvent this but then, once again, we're moving into development
> areas that need more than just a good idea for anything to happen.
> 

John's ".cgw.gz"/".cgw.bz2" would solve that, or we can use ".cgw" for
gzipped and ".cg2" for bzip2ed (apologies for the horrendous neologism :-))

Regards,

	Bernard

--------------------------------------------
Bernard Dautrevaux
Microprocess Ingenierie
97 bis, rue de Colombes
92400 COURBEVOIE
FRANCE
Tel:	+33 (0) 1 47 68 80 80
Fax:	+33 (0) 1 47 88 97 85
e-mail:	dautrevaux AT microprocess DOT com
		b DOT dautrevaux AT usa DOT net
-------------------------------------------- 

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/