Linked by Hadrien Grasland on Sat 8th Jan 2011 19:28 UTC, submitted by sjvn
Permalink for comment 456637
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
More Features »
Sponsored Links



Member since:
2007-02-17
If you write your own code, it is your code, so you may do with that whatever you wish.
If you don't write code, GPL software won't bite you, you know. You are absolutely free to run it without restriction. Fill your boots. Have a ball.
If you want to use someone else's GPL code in conjunction with your work, keep it separated from your work. Do not include any GPL source code actually within your work, but rather write your own code to run "on top of" GPL code. Here is an example of a company with a proprietary product which has done just that:
http://www.bricsys.com/common/news.jsp?ksearch=Linux
If you want to re-distribute someone else's GPL code, then simply re-distribute their source code as well. Its their code anyway, no skin of your nose to re-distribute it even as source code.
You do not have to distribute source code for your work, if you do not want to, if it was actually your work.
So, please explain, what exactly is your reason for avoiding GPL code? I'm peplexed, I truly am.