GCC unplugged

>If I create a copyrighted work and you put it on a disk with some other stuff and mass
produce it, your product, the resulting disk is a derivative work and would constitute a
copyright infringement unless you received a license which permitted you to perform this
action. Full stop. When your work actually contains my copyright work, it's derivative.

I'm not sure that's accurate in detail -- my understanding is that putting several works next
to each other on one medium, individually unmodified, is not creating a derivative work; it's
just putting several works together, and distributing the result is like distributing each of
those works individually.  (In particular, while there is such a thing as a compilation
copyright, it is distinct from the copyright inherent in a derivative work.)

However, I am not a lawyer or any other kind of expert.  Rick Moen will swoop in momentarily
to tell us both off, possibly in iambic pentameter (he's just that cool).

In any case, it's hardly relevant to the point at hand.  Obviously I agree that we don't need
to ask a judge to know that it's illegal to distribute a copyrighted work verbatim, without a
valid license.  But who cares whether this is technically a contradiction to my original point
or not... do you really think anyone was confused?  I was responding to a poster claiming they
could make some works derivative by adding a line to their license, which is nonsense...

>In the cases of interest, where someone has extended something like GCC with some proprietary
module, it is sufficient for the license of GCC to say that you can not distribute GCC with
proprietary extensions and define proprietary extensions in whatever way the copyright holder
pleases.

1) Defining "proprietary extensions" is a pain in the butt.  Can I ship GCC and Matlab
together?  Matlab contains proprietary code that knows how to call GCC to build Matlab
plugins...

2) This would make the GCC license GPL-incompatible.

>It's true that someone could still distribute the proprietary extensions *without GCC*, and
"only a judge could decide" that the proprietary work work still infringed on the GCC license
even though GCC itself was not being distributed, but when we're talking about proprietary
extensions, the separate distribution case isn't what most people are thinking of...

But, uh... that's *exactly* how people have tried to weasel around this problem both
historically (Apple with Objective-C, say) and right now (e.g. NVidia with its proprietary
kernel modules).  So anyone who isn't thinking about it, should be :-).

>A license [meaning contract] could prohibit users from combining the covered work with a
proprietary extension.

There are valid reasons to want to avoid restricting use, as opposed to distribution... if
nothing else, how do you phrase this in a way that allows people to make local modifications
that they do not distribute, but rules out proprietary extensions?