Bug#1131015: mention Files-Excluded/Included-* in copyright-format-1.0.xml

On Tue, Mar 17, 2026 at 02:31:30PM +0100, Simon Josefsson wrote:
> Bill Allombert <[email protected]> writes:
> 
> >> Although what do you mean packaging tools shouldn't require the use of
> >> copyright-format?  There is no requirement here, everything is opt-in.
> >> The patch document these to be optional fields, for those who want to
> >> use them as they are supported by uscan and mk-origtargz.
> >
> > Getting uscan to call mk-origtargz to remove files requires using the new
> > copyright-format. Otherwise the maintainer need to call mk-origtargz
> > manually. We should do better.
> 
> I'm not sure I follow here.  How?  From a design point of view, having a
> Files Excluded/Included wildcard list seems like a reasonable approach.
> And people will need to opt-in to use some mechanism, or do things
> manually.

mk-origtargz does not process Files-Excluded in debian/copyright if
debian/copyright is not in the new copyright-format.

> Is your concern that the existing fields hi-jack the debian/copyright
> file, when those fields could have been put in a different file?

Indeed.

Cheers,
Bill.