Bug#489135: debian-policy: how to document a repackaged .orig.tar.gz
On Thu, 2008-07-03 at 10:45 -0700, Russ Allbery wrote:
> Bart Martens <bartm@debian.org> writes:
>
> > Package: debian-policy
> > Severity: wishlist
> >
> > Not so long ago the Developer's Reference explained how a repackaged
> > upstream tarball must be documented in debian/README.Debian-source. Now
> > the Developer's Reference states that this must be documented in
> > debian/copyright.
> >
> > developers-reference 3.4.0 :
> > file:///usr/share/doc/developers-reference/best-pkging-practices.html#bpp-origtargz
> >
> > "must contain detailed information how the repackaged source was
> > obtained, and how this can be reproduced in the
> > debian/copyright."
> >
> > Please consider moving this information to debian-policy.
>
> Could you explain more of why you feel that Policy is the right place for
> this recommendation?
>
Because it is typically a "must"-rule as meant in debian-policy.
debian-policy 3.8.0.1 :
file:///usr/share/doc/debian-policy/policy.html/ch-scope.html#s1.1
"In the normative part of this manual, the words must, should
and may, and the adjectives required, recommended and optional,
are used to distinguish the significance of the various
guidelines in this policy document."
Also, developers-reference points to debian-policy for standards to
which Debian software must comply.
developers-reference 3.4.0 :
file:///usr/share/doc/developers-reference/scope.html
"Nor does this reference detail the standards to which Debian
software must comply. All of such information can be found in
the Debian Policy Manual."
When I compare debian-policy and developers-reference then I honestly
think that the part about how a repackaged upstream tarball must be
documented belongs in debian-policy.
Does this answer your question ?
Regards,
Bart Martens
Reply to: