Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Mon, 16 Dec 2002 13:12:26 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Cc: jantz DOT c DOT tran AT intel DOT com Subject: Re: Building a specific version of cygwin Message-ID: <20021216181226.GA16792@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com, jantz DOT c DOT tran AT intel DOT com References: <331AD7BED1579543AD146F5A1A44D52509322A AT fmsmsx403 DOT fm DOT intel DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i On Mon, Dec 16, 2002 at 12:29:55PM -0500, Igor Pechtchanski wrote: >On Mon, 16 Dec 2002, Tran, Jantz C wrote: >>Is there any way I can get the source to specific versions of the >>Cygwin source (via CVS or otherwise). I'm primarily interested in >>being able to build 1.3.1 and 1.3.9. Thanks in advance. > >Some (unfortunately, not all) of the releases are tagged in CVS. As >far as I can see, there are tags for both of those you need. A "cvs >log" would have shown that to you. The releases are tagged for my benefit when I make a release. I make no effort to ensure that any tag you see in CVS actually reflects the same numbered cygwin release. Also, since newlib and other components aren't tagged, it isn't possible to recreate a release exactly. As has been frequently mentioned, with a couple of very minor exceptions, cygwin releases are always backwards compatible. So, 1.3.18 DLLs should be able to handle executables built with 1.1.1. cgf -- 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/