pkgsrc-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: pkg/47418: pkgin cannot identify upstream version



The following reply was made to PR pkg/47418; it has been noted by GNATS.

From: George Georgalis <george%galis.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: pkg-manager%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, 
pkgsrc-bugs%netbsd.org@localhost
Subject: Re: pkg/47418: pkgin cannot identify upstream version
Date: Tue, 15 Jan 2013 15:55:46 -0800

 On Sun, Jan 13, 2013 at 12:25 PM, David Holland
 <dholland-pbugs%netbsd.org@localhost> wrote:
 >
 > The following reply was made to PR pkg/47418; it has been noted by GNATS.
 >
 > From: David Holland <dholland-pbugs%netbsd.org@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc:
 > Subject: Re: pkg/47418: pkgin cannot identify upstream version
 > Date: Sun, 13 Jan 2013 20:21:03 +0000
 >
 >  On Mon, Jan 07, 2013 at 10:25:01PM +0000, george%galis.org@localhost wrote:
 >   > This is a feature request to identify the upstream src directly
 >   > with pkgin. This would be useful to identify best package to use
 >   > when there are multiple options, it is not always clear which
 >   > represents the newest release.
 >   >
 >   > [...]
 >   >
 >   >  pkgin search firefox
 >   > firefox36-l10n-3.6.28  Language packs for www/firefox36
 >   > firefox36-3.6.28nb4  Web browser with support for extensions
 >   > firefox10-l10n-10.0.6  Language packs for www/firefox
 >   > firefox10-10.0.7nb3  Web browser with support for extensions
 >   > firefox-l10n-15.0.1  Language packs for www/firefox
 >   > firefox-15.0.1nb2    Web browser with support for extensions
 >   >
 >   > but how would one determine if firefox36 or firefox represents the
 >   > most current upstream package available?
 >
 >  Well, in this case because 15.0.1 > 10.0.7 > 3.6.28.
 >
 >  I agree this isn't abundantly clear in a number of cases. But I think
 >  this is best handled by improving the COMMENT values for these
 >  packages, e.g.
 >
 >    firefox36-l10n-3.6.28  Language packs for www/firefox36
 >    firefox36-3.6.28nb4  Web browser with support for extensions (version 
 > 3.6.x)
 >    firefox10-l10n-10.0.6  Language packs for www/firefox
 >    firefox10-10.0.7nb3  Web browser with support for extensions (version 
 > 10.x)
 >    firefox-l10n-15.0.1  Language packs for www/firefox
 >    firefox-15.0.1nb2    Web browser with support for extensions (version 
 > 15.x)
 
 
 I like it, that would certainly be clearer while selecting packages.
 Do you know a url for naming/numbering convention? cause that wasn't
 obvious to me.
 
 I do have a need for the original source url too. For the purpose of
 downloading original sources and respective licenses in a corporate
 environment where versions, licenses and the code base is tracked. I
 appreciate the challenge of mirror site urls, but the issue is not
 traceability to the url the code is obtained from, so any url should
 work as long as packages is the same.
 
 --
 George Georgalis, (415) 894-2710, http://www.galis.org/
 


Home | Main Index | Thread Index | Old Index