Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.com
Message-ID: <3B9439B2.3020707@ece.gatech.edu>
Date: Mon, 03 Sep 2001 22:17:22 -0400
From: Charles Wilson <cwilson@ece.gatech.edu>
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: cygwin@cygwin.com
Subject: Re: press for cygwin
References: <17B78BDF120BD411B70100500422FC6309E334@IIS000> <3B939A12.5040009@ece.gatech.edu> <20010903111442.D2024@redhat.com> <999555859.31754.24.camel@lifelesswks> <20010903212347.A3959@redhat.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Christopher Faylor wrote:


> "My name is Inigo Montoya, you are the program that ruined my cygwin
> distribution.  Prepare to die!"


HA!  I *love* that movie -- and the book is abso-stinkin' hilarious!

On the actual topic, I've changed my mind.  I thought that using a 
unique extension to indicate that *our* .tar.bz2 file (.cyg) followed 
some special internal format (/etc/postinstall, <top>/CYGWIN-PATCHES/, 
etc) would be a good idea.

Then i realized that I've been using setup.exe (with a custom setup.ini) 
to install custom tarballs -- that don't follow that special format -- 
into my cygwin for months now.

Nope, keep it .tar.bz2, if you don't mind. :-)

--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/

