Re: Bug#758124: Documenting the Testsuite field in the Policy.
On Tue, Aug 19, 2014 at 07:35:22PM -0300, Antonio Terceiro wrote:
> >
> > Anybody Developer who thinks that 1) the Policy is useful and 2) the Testsuite
> > field is useful, can participate. What is needed is to read the text below,
> > verify that it reflects the facts, and if yes, send an email containing
> > something like “seconded”.
>
> IMO the fact that close to 600 packages are already using the field
> shows quite some support for it to be documented. :)
I somehow was guided by this idea when I was raising my hand the first
time. And yes, I agree that we should document what we are using.
> > > > > + <heading><tt>Testsuite</tt></heading>
> > > > > +
> > > > > + <p>
> > > > > + Simple field containing a comma-separated list of values allowing
> > > > > + test execution environments to discover packages which provide
> > > > > + tests. Currently, the only defined value is <tt>autopkgtest</tt>.
> > > > > + </p>
> > > > > +
> > > > > + <p>
> > > > > + This field is automatically added to Debian source control files by
> > > > > + <prgn>dpkg</prgn><footnote>from version 1.17.11.</footnote> when
> > > > > + a <file>debian/tests/control</file> file is present in the source
> > > > > + package. This field may also be used in source package control
> > > > > + files if needed in other situations.
> > > > > + </p>
>
> Looks good to me. Seconded, FWIW.
I wonder whether the second paragraph implies something like: "Since the
field is automatically added there is no reason to specify it explicitly
any more." I think this policy change is even implemented in lintian since
I think to remember that lintian stopped warning about the missing testsuite
field (if I remember correctly without checking).
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: