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 Message-ID: <000401c3091c$d178e040$5c16989e@oemcomputer> Reply-To: "Peter S Tillier" From: "Peter S Tillier" To: "Cygwin" References: <000201c30915$dcf96180$5c16989e AT oemcomputer> <001101c30917$fbf597a0$78d96f83 AT pomello> Subject: Re: Cygwin patch numbers Date: Tue, 22 Apr 2003 23:16:25 +0100 X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Max Bowsher wrote: > Peter S Tillier wrote: >> Folks, >> >> I notice that the Cygwin developers use a standard naming convention >> for the packages containing, for example gawk and sed. This >> convention is based upon the tool's version number and various patch >> levels, such as: >> >> gawk-3.1.2-2.tar.bz2 >> >> 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 Robert Collins points out that the -2 is the package release number. >> in the version number for each tool/package please? > > I doubt that most Cygwin package maintainers are going to hunt out > version strings and change them - especially since this part of a > patch would cause a conflict every time they started work on a new > version. > Fair enough, it was just a thought. > In any case: > > $ cygcheck -c gawk > Cygwin Package Information > Package Version > gawk 3.1.2-2 > > Use -h to see help about each section > $ I use this quite often when I'm not sure about current versions, but thought that the tool's "--version" number would be more useful. Regards, Peter S Tillier "Who needs perl when you can write dc, sokoban, arkanoid and an unlambda interpreter in sed?" -- 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/