Re: pkg/47418 (pkgin cannot identify upstream version)

[George Georgalis <george%galis.org@localhost>]

The State-Changed-Why open->closed indicates jperkin doesn't understand this request or the value of it.

It would be _very_ valuable to query the actual source file used by pkgsrc (url, and revision if it is a repo), vs what is currently in use on the website.

ie, the change-request is to provide a reporting of the version configuration USED by pkgsrc.

This has value for research of installed packages as well as packages considered for installation.

It will address the situation of a known feature or bug (per HOMEPAGE) and determination if pkgsrc is inclusive.

On Mon, Apr 20, 2020 at 3:50 AM <jperkin%netbsd.org@localhost> wrote:

Synopsis: pkgin cannot identify upstream version

State-Changed-From-To: open->closed
State-Changed-By: jperkin%NetBSD.org@localhost
State-Changed-When: Mon, 20 Apr 2020 10:50:30 +0000
State-Changed-Why:
The firefox-related parts of this PR were resolved a while back.  As for
the pkgin parts, you can identify the HOMEPAGE of a package using pkgin
with "pkgin pkg-build-defs <pkg> | grep HOMEPAGE", and from that be able
to find the source files, or grep for PKGPATH to find where all the pkgsrc
related files are kept for the package in question.

--

George Georgalis, (415) 894-2710, http://www.galis.org/