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: <3B042DC8.F96AF022@ece.gatech.edu> Date: Thu, 17 May 2001 16:00:08 -0400 From: Charles Wilson X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: bkeener@thesoftwaresource.com CC: cygwin@cygwin.com Subject: Re: Thanks for cygwin's setup.exe -- and a suggestion References: <200105171726.NAA20127@envy.delorie.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Brian Keener wrote: > > DJ Delorie wrote: > > Or, get the source tarball for cygwin itself, from any cygwin mirror. > > > DJ, > > I haven't look at those before - how often do they get rebuilt to stay in > sync with what's in cvs. > Depends on what you mean. The setup.exe contained within each cygwin-inst-yyyymmdd tarball is (of course) up-to-date with the indicated yyyymmdd. However, the setup.exe distributed directly from the http://www.cygwin.com/ webpage is not updated very often. Last time I checked (about a week ago) it was still v2.29 (e.g. 1.1.8-1 timeframe). Current cvs setup.exe reports approx. 2.45 or so. I think cgf is still waiting for feedback on the .bz2 stuff he recently added before updating the setup.exe on the webpage. --Chuck -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple