Sorry can't read thats an app not OS component...it wouldnt let me edit![]()
They distribute it with the OS, and the point of my hypothetical was the judge ruled that all those bits on the Mac OS X DVD comprise a "work," so the fact that it's an "app" seems irrelevant (to my crazy hypothetical).
what key componet distributed with OS X is GPL?
Again, it doesn't matter if it's a "key component." The judge said the entire disk is a single work. That disk includes "key components," desktop wallpapers, and games. The whole thing, according to Judge Alsup, is a single "work."
The GPL says that if you use a GPL'd component (not a "key component") as part of your "work," your "work" is GPL.
If your question is merely idle curiosity, http://www.apple.com/opensource/ lists many key components, though I don't know that they are GPL (vs. BSD, etc.) Many of the open sourced components are listed as being part of "Mac OS X" as opposed to any particular app within the OS.
Update: if it's all BSD or LGPL, that makes the hypo less fun
Update 2: randomly checked GDB's license - it's GPL, not LGPL.
Personally, I don't think so. Legally, I think it is a gray area. But we were discussing the hypothetical situation in which it did apply.
You seem to have lost track of the discussion. We were discussing how the Autodesk ruling affects Apple. I was just pointing out that ownership of a copy is an important part section 117. There are other important parts.
You are confusing ownership of a copy with ownership of the copyrighted work. Apple, Autodesk and most other major software companies claim that the copy (the DVD and the bits on the DVD) that they sell you in a retail box is licensed, not sold. Verner v Autodesk ruled that the copy is actually sold and not licensed.
But you still wouldn't have the right to install the software, because the license doesn't allow it. I would say it is absurd to claim that Section 117 would allow you to modify the software and then install it, when you wouldn't have the right to install on a 100% compatible system.
It is owned by the copyright owner (in this case, Apple). Additionally, individual copies can also be owned by other entities. This does not involve the transfer of any copyrights.
Did it? The judge seemed to tap dance around that question while establishing that the copy is owned while acknowledging apparently conflicting rulings.
I don't believe it is clear what section 117 covers.
Yes, let's think of all the people that can't afford things they want. I want a Maserati, but I can't afford it - why won't someone just come up with a way for me to get one at the price of a Kia.![]()
The GPL says that if you use a GPL'd component (not a "key component") as part of your "work," your "work" is GPL.
A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an “aggregate” if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
Not quite. The GPL explicitly says:
This is exactly what Apple is doing with Mac OS X, when they include gdb, emacs, etc...
B
Ah, but the judge said that OS X is "a work," not "an aggregate" - that's why changing a part of it is a "derivative work."
Aggregate is just a descriptor in that case (I would argue) describing it as a combination of things. I dont think that a judge is going to really care. I think for all intents and purposes they are the same thing. My guess is that the difference is that a work can be a larger envelope that can contain an aggregate.
Well, I guess the question is do you apply the GPL provisions about "work" or the GPL provisions about "aggregate?" They're not the same thing with respect to the GPL, and we now have a court that says that Mac OS X is a "work."
I wonder if they can be both depending on what the nature of the case would be. The psystar case was about osx as a whole as a copywritten entity and not about the open source components or any one component.
Well, I guess the question is do you apply the GPL provisions about "work" or the GPL provisions about "aggregate?" They're not the same thing with respect to the GPL, and we now have a court that says that Mac OS X is a "work."
My links about Steve's underhanded dirty tricks and cheating are from Woz and other historians. No one can refute the facts about the Atari/Apple connection except to say "its not true" or "don't talk about that, it didn't happen". Well, I have links that suggest otherwise. A zealot like you will never see Apple as the ruthless corporation that it is.
Apple sued Psystar to prevent anyone from competing with Apple with a clone. They're as nasty as they are because they have Steve. He's an expert at playing rough and dirty.
Well, I guess the question is do you apply the GPL provisions about "work" or the GPL provisions about "aggregate?" They're not the same thing with respect to the GPL, and we now have a court that says that Mac OS X is a "work."
Hey genius it takes time to compile a lawsuit.![]()
I'm not even a student but wouldn't the GPL licence override Apple Licence?
That's exactly what's the GPL is for. If you use GPL'ed work and modify it your whole program falls under the GPL. Otherwise the GPL would be pretty useless. That's why most libraries are now LGPL.
So if Apple used some components that were under the GPL then the derived work now is also under the GPL and Apple has to release its source code:
"(...)
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License. (...)
These requirements apply to the modified work as a whole. "
A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an aggregate if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
"Your honor, we cannot ignore th plain language of the GPL. it couldn't be any clearer. If a work contains GPL code, the work can only be distributed under the GPL. As the Court has correctly determined after much testimony from Apple and based on Apple's own evidence and pleadings, OS X is a work. Therefore, since it contains GPL code..."
I'm just saying that if I was Apple's lawyer, I would have been unhappy with the use of the term "work"
An aggregate is a work, it's not necessarily a derivative just because it includes some GPL code
You're making a big deal out of nothing. An aggregate is a work, it's not necessarily a derivative just because it includes some GPL code (not to mention not all open source licenses are compatible which would be a big mess if a distribution were a derivative work of all it's included packages).
There is plenty of other examples out there that would make such an argument get thrown out before the lawyer even finishes the sentence.