Re: pkg/47418: pkgin cannot identify upstream version

[David Holland <dholland-pbugs%netbsd.org@localhost>]

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)
 
 or something like that.
 
  > If there is a way to determine url for upstream sources with pkgin,
  > I don't see it. Not sure the best way to integrate with existing
  > command line, but I feel this would be a valuable option.
 
 There isn't; this info isn't stored in the package. I suppose it could
 be; it gets a bit tricky with mirror sites though.
 
 -- 
 David A. Holland
 dholland%netbsd.org@localhost