Re: Please help test new pkgin

[Jonathan Perkin <jperkin%joyent.com@localhost>]

* On 2018-06-11 at 16:38 BST, Matthias Ferdinand wrote:

> On Mon, Jun 11, 2018 at 04:10:11PM +0100, Jonathan Perkin wrote:
> > * On 2018-06-11 at 15:58 BST, Matthias Ferdinand wrote:
> > > I attached a patch to make this build date check optional ("-B" as in
> > > Build-Date).
> > 
> > Sorry but I'm not going to accept any patches to make this optional,
> > it is now considered a core requirement.
> 
> I seem to remember that packages that were actually supposed to be
> updated from repositories would get an explicit change in version number
> (revbump), e.g. increasing the nb patch level number.
> 
> But yes, it would happen ever so often that e.g. a libboost update was
> not followed by the necessary revbump of say libreoffice.

Right, this is the main problem, and one we run into relatively often,
especially on macOS.  This is only one part of the solution, we also
want to implement changes to builds so that PROVIDES and REQUIRES are
checked against any previous version of the package, which will help
to expose missed revbumps.

> > modified.  This is possible with pbulk, I've never used pkg-rr but I
> > assume it has something similar.
> At some point there was a "-U" option to this effect, but since recently
> it seems to be gone.
> 
> If you insist on BUILD_DATE checking being the default, then how about
> providing the ability to switch it off on purpose?

If pkgin ever grows a config file then I may add it as an advanced
option for users who want a "shut up and do what I want even if it's
wrong" override.  It wouldn't be much use as a command line option as
you'd be forced to use it for every single invocation which would get
old fast.

-- 
Jonathan Perkin  -  Joyent, Inc.  -  www.joyent.com