On Tue, Jun 12, 2018 at 07:30:03PM +0200, Paul Gevers wrote:
> Hi Ian,
>
> On 12-06-18 17:51, Ian Jackson wrote:
> > Paul Gevers writes ("autopkgtest needs-recommends [Was Re: autopkgtest: versioned triggers and fixing "Test dependencies are unsatisfiable with using apt pinning"]"):
> >> tl;dr: autopkgtest restriction "needs-recommends" and using aspcud
> >> solver is horror. How to move forward?
> > ...
> >> 2) Stop supporting needs-recommends and use the aspcud solver in a way
> >> similar to what I implemented on salsa. Clearly this restriction has
> >> been out there for a while. Will be painful for some (how many?)
> >> packages as their autopkgtest will suddenly break.
> >
> > I don't understand the history of the needs-recommends restriction,
> > but can't it be worked around in each package by explicitly listing
> > the needed recommends as direct test dependencies ?
>
> Yes. That is the work-around that would be required to deprecate this
> restriction.
I am probably missing something, but why not just injecting the packages
in Recommends: in the test dependencies when the test specifies
needs-recommends?
i.e. for the following package:
Package: foo
Depends: bar
Recommends: qux
these test definitions should be equivalent:
Test: test-foo
Restrictions: needs-recommends
Test: test-foo
Depends: @, qux
Attachment:
signature.asc
Description: PGP signature