On Sat, Jun 12, 2010 at 12:24:07 -0700, Russ Allbery wrote: > - <tag><tt>Build-Depends-Indep</tt>, > - <tt>Build-Conflicts-Indep</tt></tag> > + <tag><tt>build</tt>, <tt>build-indep</tt>, <tt>binary</tt>, > + and <tt>binary-indep</tt></tag> > <item> > - The <tt>Build-Depends-Indep</tt> and > - <tt>Build-Conflicts-Indep</tt> fields must be > - satisfied when any of the following targets is > - invoked: <tt>build</tt>, <tt>build-indep</tt>, > - <tt>binary</tt> and <tt>binary-indep</tt>. > + The <tt>Build-Depends</tt>, <tt>Build-Conflicts</tt>, > + <tt>Build-Depends-Indep</tt>, and > + <tt>Build-Conflicts-Indep</tt> fields must be satisfied when > + these targets are invoked. > </item> > </taglist> > </p> > - > </sect> > - > </chapt> > This keeps the inconsistency between policy and actual practice about what needs to be installed for the 'build' target, but I assume this is intended? Cheers, Julien
Attachment:
signature.asc
Description: Digital signature