To view parent comment, click here.
To read all comments associated with this story, please click here.
Here is the actual opinion of the FSF on this topic, in their own words, without any agenda-driven interpretations on top of it:
http://www.gnu.org/licenses/gpl-faq.html#DoesUsingTheGPLForAProgram...
A: Yes, because the copyright on the editors and tools does not cover the code you write. Using them does not place any restrictions, legally, on the license you use for your code.
The FSF opinion in relation to the copyright law requirement that a derived work results only when a major element of an original work is INCLUDED in another work:
A: Yes, you do. “Fair use” is use that is allowed without any special permission. Since you don't need the developers' permission for such use, you can do it regardless of what the developers said about it—in the license or elsewhere, whether that license be the GNU GPL or any other free software license.
QED. It turns out that the FSF do indeed understand copyright law, and it is only you who is confused.
Your references are now TRIPLY irrelevant to the original question. (PathScale's views are only SINGLY irrelevant).
You are utterly incorrect on this topic, not only according to copyright law itself, but also according to the FSF.
Edited 2011-06-16 04:54 UTC
Sorry, I should have expressed that differently.
It should have read as follows:
"Your mistaken interpretation of FSF's views on this topic are now TRIPLY irrelevant to the original question. PathScale's views, whatever they may be, are only SINGLY irrelevant."
lemur2,
"Q: Can I use GPL-covered editors such as GNU Emacs to develop non-free programs? Can I use GPL-covered tools such as GCC to compile them?
A: Yes, because the copyright on the editors and tools does not cover the code you write. Using them does not place any restrictions, legally, on the license you use for your code."
The answer above is (apparently) referring to this snippet:
"The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does."
So it's clear cut for editors, but it's not so obviously simple for things like compilers.
"Q: Do I have “fair use” rights in using the source code of a GPL-covered program?
A: Yes, you do. 'Fair use' is use that is allowed without any special permission. Since you don't need the developers' permission for such use, you can do it regardless of what the developers said about it—in the license or elsewhere, whether that license be the GNU GPL or any other free software license."
No copyright holder can restrict fair use rights, but I don't see how this is at all relevant to this discussion? Are you suggesting that we have a fair use right to use GCC without a license? I really don't understand what you are getting at.
"QED. It turns out that the FSF do indeed understand copyright law, and it is only you who is confused."
Perhaps I am, but I brought up relevant points, and it appears that you are no less confused than I am.
"Your references are now TRIPLY irrelevant to the original question. You are utterly incorrect on this topic, not only according to copyright law itself, but also according to the FSF."
Wow...what did I trigger to make you lash out like this? While you were counting irrelevant levels of irrelevance, I think you forgot to ponder why the FSF has GPL exceptions for GCC.





Member since:
2011-01-28
lemur2,
"So the only sane conclusion from this observation is that whatever the FSF might believe in this scenario is DOUBLY irrelevant."
I didn't mean to imply the FSF has any say over EKOPath. If PathScale took the same stance as the FSF but uses the GPL without exceptions, it could be their intent that the open source EKOPath should only be used for GPL code.
I agree it sounds ridiculous, but your earlier post made it sound like you weren't aware of the exceptions for GCC, which is why I brought them up.
Edited 2011-06-16 04:33 UTC