Hi Paul, On Sat, Jan 06, 2024 at 01:12:50PM +0800, Paul Wise wrote: > On Mon, 2024-01-01 at 13:16 -0800, Ross Vandegrift wrote: > > > Suppose project A includes code from project B. > > The best option would be to talk to upstream about removing the copy, > further advice about embedded copies is on the wiki: > > https://wiki.debian.org/EmbeddedCopies Definitely agreed in general. I had a different kind of situation in mind. Imagine I take some code from a freely licensed reference implementation and customize it. The result is a derived work. But this embedding isn't removable - the reference implementation shouldn't accept changes to integrate it into a specific project. It'd be reasonable to include the original license and copyright statements. If I do, Debian requires packagers to describe the license and copyright on those embedded license/copyright files. And I'm puzzled about how to do that best. Maybe the answer is to repack it away? But that seems weird. It's freely redistributable, and that'd be *obscuring* license/copyright details. We usually like that. :) The same issue arises for disabled conveience copies. The wiki suggests Files-Excluded, but also alternatives that involve Debian redistributing the convenience copy (and so probably it's license/copyright files) in source packages. (I realize not much hangs on this - but cme/licensecheck raised the issue to me. I can ignore it, but also got curious and tried to figure out what to do.) > > How should these files appear in d/copyright? > > (Please CC me, I'm not subscribed.) > > Richard Laager responded but forgot to CC you, I bounced the message: > > I document them the same, except that I also add use the DEP-5 "Comment" > field to indicate that it came from "B". Thanks! Ross
Attachment:
signature.asc
Description: PGP signature