Le Wed, Jul 14, 2010 at 09:23:02AM -0700, Russ Allbery a écrit : > > diff --git a/policy.sgml b/policy.sgml > index 3e99099..9fe7158 100644 > --- a/policy.sgml > +++ b/policy.sgml > @@ -476,9 +476,11 @@ > <item> > must not require a package outside of <em>main</em> > for compilation or execution (thus, the package must > - not declare a "Depends", "Recommends", or > - "Build-Depends" relationship on a non-<em>main</em> > - package), > + not declare a <tt>Pre-Depends</tt>, <tt>Depends</tt>, > + <tt>Recommends</tt>, <tt>Build-Depends</tt>, > + or <tt>Build-Depends-Indep</tt> relationship on a > + non-<em>main</em> package unless a package > + in <em>main</em> is listed as an alternative), > </item> > <item> > must not be so buggy that we refuse to support them,
Dear all, I also have mixed feelings about aligning Policy on current practices: on systems where the contrib and non-free archives are not enabled, this brings unavailable packages in the part of the dependancy graph that is supposed to be closed in stable releases. However, I admit that the wording of the release goal would allow to list unavailable packages as alternatives. Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100714232700.ga16...@merveille.plessy.net
