Mail Archives: cygwin/2003/04/23/09:08:39
Warren Young wrote:
> 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?
RPM forces this, doesn't it?
> 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
> $
It's slow, and only gets the package name, but this may help:
zgrep -F `which gawk | sed -e s,^/,,` /etc/setup/*.lst.gz \
| sed -e 's,^/etc/setup/\(.*\)\.lst\.gz:.*$,\1,'
You could conceivably put that in a script and feed the result to cygcheck
to get the full version info.
Max.
--
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 -