Re: GPL only modules

From: Paul Mackerras
Date: Mon Dec 18 2006 - 19:43:48 EST


Linus Torvalds writes:
>
>
> On Tue, 19 Dec 2006, Paul Mackerras wrote:
> >
> > There is in fact a pretty substantial non-technical difference between
> > static and dynamic linking. If I create a binary by static linking
> > and I include some library, and I distribute that binary to someone
> > else, the recipient doesn't need to have a separate copy of the
> > library, because they get one in the binary.
>
> I agree, and I do agree that it's a real difference.
>
> I personally think that it's the "aggregation" issue, not a "derivation"
> issue, but I'll freely admit that it's just my personal view of the
> situation.

I think the critical issue is whether any human creativity is required
to establish derivation.

Clearly there is some modification and adaptation that ld does to a
library in the process of linking it into a binary, and ld is unlike
mkisofs or gzip in that you can't extract the library in its original
form (or any form suitable for linking with another program) from the
output of ld --static.

The question is whether it matters that the process that ld does is
mechanical in nature. This is possibly an area where you'll get a
different answer in different jurisdictions. I believe that in the
US, some creative input is required to establish copyright, whereas in
Australia, only "effort" is needed. I don't know whether that affects
the definition of "derived work".

I personally would think that a mechanical process of modification
*does* create a derived work, but it would take a court of law or a
legislature to make an authoritative decision, I guess.

Paul.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/