#include <hallo.h> * Joerg Schilling [Mon, Mar 20 2006, 11:21:30PM]: > It seems that you never did read and understand the GPL :-( > > The GPL is as holey as a Swiss cheese when talking about the compile > environment:
... Joerg, could you please stay ontopic and not flame? We try to discuss with you... And we *do* understand the GPL, and its not only one interpretation of the GPL. You can read our -legal list too see much more of that, please look at [URLS] for more information. Also there is AFAICS nobody happy with your efforts to restrict the GPL claiming that it gives you means to force everybody do things unrelated to GPL§2c (slandering about Linux in control output, for example). Neither does anything give you means to forbid us the replacement of license-incompatible files with GPL compatible versions. And finally, in the last mail I have already presented the exact chain of conclusions, including the intent of the OP. I expect you (as programmer knowing how logic works) to be able to find the wrong link there -- so would you consider answering this (uncomfortable) question? URLS: http://lists.debian.org/debian-legal/2006/03/msg00362.html http://lists.debian.org/debian-legal/2006/03/msg00391.html http://lists.debian.org/debian-legal/2006/03/msg00375.html http://lists.debian.org/debian-legal/2006/03/msg00376.html > If you would understand enough from the topic, you would understand that > the "related" makefiles of my software are always present under the same > license as the rest of the project but the unrelated (because project > indepentent) makefilesystem is just available under it's native license. Somehow all our other GPLed software has "related build software" either licensed under GPL compatible license (*) or beeing that far different that its maker can declare the outcome as a product rather than a derivate (compilers). Eduard.
