GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Say I write some little program. This program only compiles by using a C library that has a GPL license. When I publish my program, must I include my source code? Can I keep it closed source?
in my understanding you must release the source code to anyone who requests it. if you charge for your product then you are only obliged to provide source code to paying customers, but you must still do so if requested.
less effort... ahh i see you have the highest standard motivating you!
yes there are plenty of incompatibilities within licenses for open and closed source products, but you only provide source for things using the open source software, not the other sub components. if that were the case then those products would already be obliged to be open source.
in my understanding you must release the source code to anyone who requests it. if you charge for your product then you are only obliged to provide source code to paying customers, but you must still do so if requested.
You have to provide source to anyone who asks, whether or not they bought the product. (Section 3.b of the GPL, I believe)
well 3b says that the distributed product must contain an offer to show the source code for free. so if someone does not have that distributed product, e.g. the box set or downloaded licensed software, then they have no offer with it either.
well 3b says that the distributed product must contain an offer to show the source code for free. so if someone does not have that distributed product, e.g. the box set or downloaded licensed software, then they have no offer with it either.
Well, under the GPL FAQ you would seem to be correct. Of course, if someone you sold a copy to redistributes it, you are still obligated to support those copies with source. So imagine one person buys a copy and posts it on some FTP/torrent/whatever site...
hmm, i'd doubt that really. This would really be what centos is all about, they bought the rhn subscription to get the rhel official updates and they rebuild them. you won't get the updates for rhel without the $$$ subscription at all. once centos rebuild them, they are no longer redhat's software.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.