[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#944325: please fix this unclear and obtuse phrasing in §7.8 (suggestion provided)



Hello,

On Thu 07 Nov 2019 at 04:51PM -05, Nicholas D Steeves wrote:

> The full sentence in question is "This field should not be added
> solely for purposes other than satisfying license or DFSG requirements
> to provide full source code".
>
> "solely for purposes other than satisfying" is the problematic
> construction and should be rephrased for readability and clarity.
>
> I suggest replacing the whole sentence with "The purpose of this field
> is exclusively for cases where a package's license, or when DFSG
> requirements, necessitate its presence; Built-Using should not be used
> for any other purpose".  This is much more clear and it flows
> nicely into the next sentence "In particular, it should not be added
> solely to enable finding packages that should be rebuilt against newer
> versions of their build dependencies."

Thank you for this.  I agree that the sentence is unnecessarily hard to
read.  Perhaps you could propose a patch against policy.git.

-- 
Sean Whitton

Attachment: signature.asc
Description: PGP signature


Reply to: