Bug#489135: debian-policy: how to document a repackaged .orig.tar.gz
Bart Martens <bartm@debian.org> writes:
> On Thu, 2008-07-03 at 10:45 -0700, Russ Allbery wrote:
>> Bart Martens <bartm@debian.org> writes:
>>> 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.
This is not currently a must. Currently, people are not required to do
this at all. I guess what I'm looking for is a rationale for why this
should be an RC bug, as opposed to just a best-practice recommendation.
Or maybe it should be in Policy as a "should"?
> 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
This is currently not a standard with which people must comply. That's
what you're proposing changing by moving it into Policy. I want to
understand what problems it would solve to require this. It may very well
be something we should do, but we should understand what the rationale is.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: