Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID:	<3EA688E7.2030607@etr-usa.com>
Date:	Wed, 23 Apr 2003 06:36:55 -0600
From:	Warren Young <warren AT etr-usa DOT com>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language:	en-us, en
MIME-Version:	1.0
To:	Cygwin-L <cygwin AT cygwin DOT com>
Subject:	Re: Cygwin patch numbers
References:	<000201c30915$dcf96180$5c16989e AT oemcomputer>
In-Reply-To:	<000201c30915$dcf96180$5c16989e@oemcomputer>

Peter S Tillier wrote:
> 
> However when gawk --version is executed the version number only displays
> as 3.1.2 (the GNU awk version/patch number).  Would it be possible for
> the Cygwin patch number (the -2 above) to be included in the version
> number for each tool/package please?

Even assuming the simplest case where there's just a single file 
containing the displayed version number, it would still be a pain to 
keep the displayed package update level part in synch with in the 
package's file name.  Changing that version number usually requires 
rebuilding all of the binaries in the package, but repackaging a program 
is often done for reasons that don't in and of themselves require 
rebuilding everything.  For example, maintainers sometimes forget to 
include a file in the package.  Should they have to rebuild their whole 
package just to bump the package update level?

What I'd rather see is a move to a packaging scheme like RPM that keeps 
a database of files that belong to packages:

	$ rpm -qf `which gawk`
	gawk-3.1.2-2
	$

In the meantime, the cygcheck feature mentioned above seems to do what 
you want.


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