On Sun, Dec 10, 2017 at 10:46:12AM -0700, Sean Whitton wrote: > > One of the files inside Package A is generated during build time. > > However, the generation of the file requires Package B which has > > different copyright, and the generated file in Package A is basically > > a format conversion of the file in Package B, and the copyright needs > > to be retained per license of Package B. It could be copyright > > violation of Package B if copyright status and requirements is not > > fulfilled in Package A and we redistribute Package A. > > > > I would suggest a tag "Files-Binary" in copyright-format to fulfill > > this situation. > > What would the definition of this field be? It is not clear from your > example. Files-Binary would be package name and file path to the files which its copyright is not in source package but in binary package. For example: Files-Binary: package-a-data, usr/share/package-a-data/file-in-question Copyright: 2038 John Doe License: Expat --- Another solution to this problem is mark certain file which is generated using what source package inside the header, and during build process the copyright information requires to be attached in the binary package. This should introduce another tag "Depends", like: Files-Binary: package-a-data, usr/share/package-a-data/file-in-question Depends: package-b If the maintainer knows what specific file in package-b it requires, they can specify it like: Files-Binary: package-a-data, usr/share/package-a-data/file-in-question Depends: package-b, data/orig-file And if the specified file in package-b has the same problem of package-a, as it only exists in binary package, it can be like this: Files-Binary: package-a-data, usr/share/package-a-data/file-in-question Depends-Binary: package-b-data, usr/share/package-b-data/orig-file --- For real-world use case, I am packaging glyphslib, which has above problem for a stripped file which needs to be generated from source: https://anonscm.debian.org/cgit/pkg-fonts/glyphslib.git/tree/debian/copyright Please comment or propose another idea if the use case of them is not clear. Yao Wei
Attachment:
signature.asc
Description: PGP signature