Suggestion to add build/revision number to "pkg stats"

[Baptiste Daroussin]

On Fri, Sep 18, 2015 at 09:43:51PM +0200, Simon Wright wrote:
> On 16/09/2015 22:58, mfv wrote:
> 
> snipped
> 
> > The build number is only available when the build begins, but the
> > package upgrade is not possible until the build process ends many
> > hours later.  Moreover, it is also possible to update the port tree to
> 
> snipped
> 
> > A simple solution would be to have the build number available as part
> > of a port upgrade and made available in "pkg stats".  Its output
> > could look like this:
> >
> > Local package database:
> 
> snipped
> 
> > Even better would be an argument to "pkg stats" that would only output
> > the revision number, say "pkg stats -n"
> >
> > After running "pkg upgrade", it would then be an easy to extract the
> > build number of that particular upgrade and then sync the ports tree to
> > that number using subversion or, my favourite, svnup.
> 
> +1, this information would be very useful for me. It might be 
> necessary to be able to specify a specific repository as well as the 
> local/remote switch; I have two remotes configured, my one built by 
> poudriere and also the "latest" freebsd.org repo.
> 
> Simon.

This is a bit more complexe than that as the ports tree can be checked out from
portsnap, svn, git etc (aka different id).

The right way would be to package the ports tree itself along with other
packages so if you need to build something: pkg install ports and you are always
100% sure to be on good ports tree.

But we are not there yet :(

Best regards,
Bapt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-pkg/attachments/20150923/438024d9/attachment.bin>