[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cygwin-apps
Subject:    Re: are curr: and test: no longer accepted in .hint files?
From:       Andrew Schulman <schulman.andrew () epa ! gov>
Date:       2017-03-24 17:54:07
Message-ID: fvmadcpugte0cvf5h8o5fi5emtifsjhq9k () 4ax ! com
[Download RAW message or body]

> > > What's the supported way now to tell calm which versions are previous,
> > > current, and test when you need to override the defaults?
> > 
> > I'm assuming you have a recent cygport, which is now generating 
> > <pvr>.hint rather than setup.hint files.
> > 
> > It's not helpful to mention specific versions in a <pvr>.hint files, so 
> > curr: is not permitted, and test: is not permitted to specify a version
> > 
> > If you need to override the default version ordering, then a separate 
> > per-package override.hint [1] can be used.
> > 
> > In this case, I think all you want to do is continue to mark 2.0.0-b9-1 
> > as a 'test' version.  As discussed in [2], the current thinking is that 
> > should be achieved with a 'test:' label in the associated pvr.hint, but 
> > unfortunately, this package pre-dates the pvr.hint changes, so you'll 
> > have to use override.hint
> > 
> > [1] https://cygwin.com/packaging-hint-files.html#override.hint
> > [2] https://cygwin.com/ml/cygwin-apps/2016-12/msg00005.html
> 
> Thanks. I hadn't seen [1] yet. I'll rework the hint files.
> 
> Thanks to whoever overhauled the package maintainer's guide in the last
> year or two. The last time I looked at it, it was badly out of date. What's
> there now is good.

Hm, looking in the git log, I see it was YOU. Now abusing my authority as
Gold Star page maintainer:

Gold star awarded! https://cygwin.com/goldstars/#JTy

[prev in list] [next in list] [prev in thread] [next in thread]