I'd prefer if we would not invent a file that might duplicate the content of the d/copyright Files-Excluded field - but this seems to be some implementation detail.
You have a point there. We could use "git filter-repo --invert-paths --paths-from-file <(extract-excluded- paths d/copyright)" instead.
On the other hand: if the file isn't present anyway, why would we
list it there in the first place?
Brian:
> For example, if an individual file contains a mixture of non-dfsg stuff > and dfsg stuff that is required for building.
These cases would require some more intrusive editing. "git filter-repo" does support that: you can use a blob callback to edit individual objects.
Of course we'd have to be a bit more careful to ensure that the
callback is idempotent and all that, but again I don't see a major
problem here, other than a somewhat-annoying intermediate step
when you pull from upstream – but we also need an annoying step
when we build the next DFSG tarball, so that's no loss. :-P
-- -- mit freundlichen Grüßen -- -- Matthias Urlichs
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature