Jonathan Yu <jonathan.i...@gmail.com> writes: > I realize DEP5 and all of that stuff regarding a machine-readable > copyright isn't set yet. > > However, I've come across a case where tarballs contain files that > have various copyrights, and I'm not sure how to represent them in > d/copyright. > > For example, if an upstream module contains a Stuff.tar.gz, and that > file itself contains stuff that is all under the same license, but has > different copyright information. > > Assume Stuff.tar.gz contains files: > foo.c > bar.txt > baz.c > > And foo.c is: Copyright 2005 Some Company A > bar.txt is Copyright 2002 Some Person B > baz.c is Copyright 2002-2007 Other Fictional Entity > > How would we represent such a case? Would we need to unpack that > tarball and then reference the files appropriately?
Well, from a Policy perspective, the answer is "write clear English text explaining the situation and giving the license details." Policy is mostly mum about whether you need to bother with the individual file copyrights (as opposed to the collection copyright of the package) if the license doesn't require you to, but it's probably easier right now if you have that available to add it in. The question was previously raised on debian-devel I think about what to do with this case from a DEP5 perspective. I personally have no idea. I don't think a DEP5 copyright file provides a very good structure for talking about this sort of distribution. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
