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

Bug#685506: debian-policy: Please add field Files-Excluded to machine readable copyright files definition



Hello,

On Thu 14 Feb 2019 at 08:45PM +01, Christian Kastner wrote:

> On 2012-08-21 14:34:50 +0200 Andreas Tille <tille@debian.org> wrote:> I
> would propose the following addition to
>>
>>   http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
>>
>> ----------------------- 8< ---------------------------------------------
>> Files-Excluded
>> --------------
>>
>> Whitespace-separated list: list of patterns indicating files removed
>> from upstream source.
> It appears as if Files-Excluded in d/changelog has become a de facto
> standard in the meantime, so I'd like to ping the Policy Team and ask
> whether/when we can expect an official blessing of this standard :-)
>
> I've been updating my crufty packages and lintian has repeatedly
> reported debian-rules-contains-unnecessary-get-orig-source-target. Most
> of my targets were indeed simple calls to uscan, but I used to maintain
> a dedicated d/files-excluded file (which I'd pass on with the
> --copyright-file option) just for the Files-Excluded data.
>
> I moved everything to d/copyright now, but having this sanctioned
> officially would be welcomed by us pedants.

Contrary to an older e-mail in this bug, the consensus among the Policy
Editors is that we can add new, optional fields to the copyright-format
spec without bumping its version number.  This is because the addition
of optional fields is backwards compatible.

I have not read the whole thread, but a quick scan suggests that all we
are waiting for here is for someone to write a patch against current
Policy's master branch.

-- 
Sean Whitton

Attachment: signature.asc
Description: PGP signature


Reply to: