Bug#489135: developers-reference: uses debian-policy style wording
On Fri, 2008-07-04 at 12:05 +0200, Raphael Hertzog wrote:
> On Fri, 04 Jul 2008, Bart Martens wrote:
> > In my opinion developers-reference should not use must/should/may
> > wording, because this makes readers confuse developers-reference with
> > debian-policy.
> While I agree that we might want to avoid "must", I don't know what words
> are left if we can't use "should" to express an advice...
The following phrases may be useful in best-practice recommendations:
- "It is recommended..."
- "The packager is advised to..."
- "... is considered a good practice."
- "A commonly used approach is to..."
- "This is usually solved by..."
> > Please consider rephrasing the must/should/may parts in
> > developers-reference to convert these parts to just best-practice
> > recommendations.
> Please consider digging out the parts where we used "must" and where it's
> not backed up by a corresponding debian-policy rule. :)
One example is the part about "Repackaged upstream source".