> > Being unable to combine GPLed code with code under > some other license > > is not something you can blame on the GPL alone. > > Of course I can. The entire reason for the GPL to exist is > to prevent > combining with code under other terms. That is it's > unique feature. For instance there is an article named "GPL Hindering Two-Way Code Sharing?" http://bsd.slashdot.org/article.pl?sid=07/09/01/2333233 It discusses how the licenses act in regards to each other and code sharing. From that page a link to http://kerneltrap.org/OpenBSD/Stealing_Versus_Sharing_Code which is an interesting read as well. Here's a quote taken directly from it "if you add 'large pieces of originality' to the code which are valid for copyright protection on their own, you may choose to put a different and separate (must be non-conflicting...) license at the top of the file above the existing license." He then suggested, "if you wish for everyone to remain friends, you should give code back. That means (at some ethical or friendliness level) you probably do not want to put a GPL at the top of a BSD or ISC file, because you would be telling the people who wrote the BSD or ISC file, 'thanks for what you wrote, but this is a one-way street, you give us code, and we take it, we give you you nothing back.'" Regards, Antonio -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
