Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: <3B939A12.5040009@ece.gatech.edu> Date: Mon, 03 Sep 2001 10:56:18 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713 X-Accept-Language: en-us MIME-Version: 1.0 To: Bernard Dautrevaux CC: "'Larry Hall (RFK Partners, Inc)'" , Mark Bradshaw , "'cygwin@cygwin.com'" Subject: Re: press for cygwin References: <17B78BDF120BD411B70100500422FC6309E334@IIS000> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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. --Chuck -- 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/