Bug#685506: debian-policy: Please add field Files-Excluded to machine readable copyright files definition
On Fri, Jan 28, 2022 at 12:41:39PM +0100, Andreas Tille wrote:
)
> > > I personally would rather think that excluding files from the upstream
> > > source is a pretty good reason to make DEP5 mandatory *for these cases*.
> > > Besides a sensible way of documentation it saves maintainer time to
> > > simply use uscan to obtain a proper tarball.
> >
> > The issue is that mk-origtargz does not actually need any field from
> > DEP5, it only needs the extra fields it specifies.
>
> I can't parse this. Do you mean `man mk-origtargz` is reading fields
> that are not mentioned in DEP5. I'd say DEP5 is just older than
> Files-Excluded and the good thing about DEP5 is that it *enabled* other
> tools to parse those fields.
mk-origtargz ignore all the fields that are currently
mentionned in DEP5. The only fields that are used are the ones it
introduces. So in that sense it is not an application of DEP5.
> What I'm actually imagine is that the time I need to write this kind of
> mails I could perfectly use to convert 2-3 d/copyright files from old
> format to DEP5. And now I'm wondering why I'm not doing so ...
Do not slow down on my account!
Cheers,
--
Bill. <ballombe@debian.org>
Imagine a large red swirl here.
Reply to: