Damyan Ivanov <d...@debian.org> wrote: > [Please continue to Cc me on replies. Thanks] [...] > In the case I am after, both "works" are in the same upstream tarball, > and in the same .deb. > > The files are separate, i.e. no compilation in the C source --> object > code sense is taking place. The icons are loaded at runtime and used > in the user interface. > > Does this sound like "a mere aggregation"?
Yes, in my opinion. If you can change the icons at runtime without ill-effect (within reason - it's OK if the new icons must be the same size, for example) and it's just that they're in the same tar volume, that seems like mere aggregation to me. See also http://www.fsf.org/licensing/licenses/gpl-faq.html#MereAggregation "Where's the line between two separate programs, and one program with two parts? This is a legal question, which ultimately judges will decide. We believe that a proper criterion depends both on the mechanism of communication (exec, pipes, rpc, function calls within a shared address space, etc.) and the semantics of the communication (what kinds of information are interchanged)." I suggest that the icons are used only as runtime data and no information is interchanged with them. Hope that explains, -- MJR/slef My Opinion Only: see http://people.debian.org/~mjr/ Please follow http://www.uk.debian.org/MailingLists/#codeofconduct -- To UNSUBSCRIBE, email to debian-legal-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
