Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
In-Reply-To:	<200410010531.i915VL1a014777@a.mail.sonic.net>
To:	cygwin AT cygwin DOT com
MIME-Version:	1.0
Subject:	Re: Request for a version/ revision/ release number for the whole Cygwin release/ distribution
Message-ID:	<OF31D49A15.094B9FEA-ON86256F20.005C3613-86256F20.005CAF7D@us.ibm.com>
From:	Fred Kulack <kulack AT us DOT ibm DOT com>
Date:	Fri, 1 Oct 2004 11:52:15 -0500
X-IsSubscribed:	yes

On 10/01/2004 at 12:31:34 AM, cygwin-owner AT cygwin DOT com wrote:
Every O/S and application
I've used had a release number for the whole thing; Cygwin should as
well.
--- end of excerpt ---

At a minimum, I think that's quite an oversimplification and perhaps 
factually untrue?

Have you used a Linux distribution for example? There's a single release 
number, but its really
rather meaningless, because the first thing you do is install updates to 
various packages (possibly
including the kernel). 

That's very similar to cygwin. You have a base version of the cygwin DLL, 
and version number
for each package. 
I suspect that the best you'll have is to explicitly test and ship your 
product with a specific
version of the packages that you use.



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -