Bug#681419: Alternative main->non-free dependencies text

[Andreas Barth <aba@ayous.org>]

* Stefano Zacchiroli (zack@debian.org) [130629 09:23]:
> On Thu, Jun 27, 2013 at 04:01:21PM +0100, Ian Jackson wrote:
> >   8. The Technical Committee resolves that alternative dependencies of
> >      the form "Depends: package-in-main | package-in-non-free"
> >      constitute a non-release-critical violation of the policy
> >      clause cited in point 1.
> > 
> >   9. When it is necessary to provide a reference in a Depends or
> >      Recommends from main to non-free, this should be done via a
> >      neutrally named virtual package.
> > 
> >  10. The Technical Committee requests that the policy editors make
> >      an appropriate clarification to the policy documents.
> 
> About point (9.), and considering the past discussion on the matter
> we've had with Colin [1], I suggest to expand it as follows:
> 
>   9. When it is necessary to provide a reference in a Depends or
>      Recommends from main to non-free, this should be done via a
>      neutrally named virtual package. When depending on such a virtual
>      package, other packages should specify a real package in main as
>      the first alternative, e.g.
>      "Depends: package-in-main | virtual-interface".

The second is already part of the policy, so I prefer to write it as
"(As already documented today, when depending on a virtual package, a
real package in main should be specified ...".

However, for recommends there might be cases where this is not
possible (because there are only non-main-packages), and this case is
not considered RC right now. This is the more interessting point for
me.



Andi