From: morrison <mor...@pu...> - 2002-05-02 14:13:25
|
Hi, I am in the process of writing a gui for components such as cdrdao. I have not decided on the license I am going to release my program under but am I correct that to comply with the GPL I just have to provide my users with a link to the cdrdao site on sourceforge which now has the sources for cygwin posted as well as the cdrdao sources. Thanks for your help. Jamie Osborne |
From: Jonas M. <jm...@ab...> - 2002-05-02 15:16:35
|
Hello, I am not a lawyer, and not a copyright holder of cdrdao. Keeping that in mind here is my interpretation: There are two issues here. First the license of your program: a) If you link dynamically with cdrdao you have to license your program under the GPL. b) If your programs forks and executes cdrdao (ie doesn't link dynamically), you don't have to do anything to comply with the GPL. And then the issue of cdrdao: a) If you do not distribute cdrdao in binary form, you do not have to do anything. b) If you distribute cdrdao binaries, well, then it gets a little bit complicated (item 3 in the GPL). There are really too many unknown variables for me to give any advice... On Thu, May 02, 2002 at 02:54:21PM +0100, morrison wrote: > Hi, I am in the process of writing a gui for components such as cdrdao. > > I have not decided on the license I am going to release my program under but > am I correct that to comply with the GPL I just have to provide my users > with a link to the cdrdao site on sourceforge which now has the sources for > cygwin posted as well as the cdrdao sources. > > Thanks for your help. > > Jamie Osborne > > > > > > _______________________________________________________________ > > Have big pipes? SourceForge.net is looking for download mirrors. We supply > the hardware. You get the recognition. Email Us: ban...@so... > _______________________________________________ > Cdrdao-devel mailing list > Cdr...@li... > https://lists.sourceforge.net/lists/listinfo/cdrdao-devel -- Jonas Munsin <jm...@ik...> KeyID: 1024/98A0C47D PGP Key fingerprint 9F 69 9D 96 80 DD 8E D0 D8 A0 30 66 F9 55 63 B4 Debian GNU/Linux | PhD student @ Embedded Systems Lab / TUCS |
From: morrison <mor...@pu...> - 2002-05-02 15:32:48
|
Thanks for your reply Jonas > a) If you link dynamically with cdrdao you have to license your program under > the GPL. > > b) If your programs forks and executes cdrdao (ie doesn't link dynamically), > you don't have to do anything to comply with the GPL. > > And then the issue of cdrdao: > > a) If you do not distribute cdrdao in binary form, you do not have to do > anything. > > b) If you distribute cdrdao binaries, well, then it gets a little bit > complicated (item 3 in the GPL). There are really too many unknown variables > for me to give any advice... My program just builds a command line and executes the compiled cdrdao binary . The binaries are to be distributed with my program so I guess I just have to supply the user with the means to get the source by way of posting them on my site or linking to the cdrdao soundforge site. |
From: Jonas M. <jm...@ik...> - 2002-05-03 18:12:05
|
Hello, I am CC:ing this to gn...@gn..., maybe someone there has time to clarify if a README file constitutes "a written offer" (see my third pharagraph bellow). On Thu, May 02, 2002 at 04:32:46PM +0100, morrison wrote: > My program just builds a command line and executes the compiled cdrdao > binary . The binaries are to be distributed with my program so I guess I > just have to supply the user with the means to get the source by way of > posting them on my site or linking to the cdrdao soundforge site. Linking to the cdrdao sourceforge site isn't enough, I think. If you provide the binaries, you have to accompany the source or a written offer on how to obtain the source, unless you distribute the unmodified binaries noncomercially and got it from someone distributing it with a written offer on how to get it; in that case you can just "redistribute" that written offer... See http://www.gnu.org/copyleft/gpl-faq.html#WhatDoesWrittenOfferValid and item 3 in the GPL. Now, I'm not 100% what "a written offer" means; does the README that comes with cdrdao, containing a link to the sourceforge site, constitute "a written offer" on how to get the source code? In that case you can just add that to your site. The cdrdao source code isn't that large, so the easiest way is just to put those on your site, too. (If you also distribute the windows binaries you also have to provide the cygwin source code, and that is quite large IIRC). -- Jonas Munsin <jm...@ik...> KeyID: 1024/98A0C47D PGP Key fingerprint 9F 69 9D 96 80 DD 8E D0 D8 A0 30 66 F9 55 63 B4 Debian GNU/Linux | PhD student @ Embedded Systems Lab / TUCS |
From: morrison <mor...@pu...> - 2002-05-03 19:16:03
|
Thanks Jonas, As far as I can tell the purpose of the GLP in this respect is to ensure that the sources are immediatly availiable to anybody that may require them. At the moment I have a link on my program's about box, a link in my program's readme file and, of course, links in cdrdao's own readme file contained with the binaries. The GPL is indeed a strange document, thanks for the link to the FAQ - I will read it now. Jamie ----- Original Message ----- From: "Jonas Munsin" <jm...@ik...> To: "morrison" <mor...@pu...> Cc: <cdr...@li...>; <gn...@gn...> Sent: Friday, May 03, 2002 7:07 PM Subject: Re: [Cdrdao-devel] Regarding GPL compliance > Hello, > > I am CC:ing this to gn...@gn..., maybe someone there has time to clarify if a > README file constitutes "a written offer" (see my third pharagraph bellow). > > On Thu, May 02, 2002 at 04:32:46PM +0100, morrison wrote: > > My program just builds a command line and executes the compiled cdrdao > > binary . The binaries are to be distributed with my program so I guess I > > just have to supply the user with the means to get the source by way of > > posting them on my site or linking to the cdrdao soundforge site. > > Linking to the cdrdao sourceforge site isn't enough, I think. If you provide > the binaries, you have to accompany the source or a written offer on how to > obtain the source, unless you distribute the unmodified binaries noncomercially > and got it from someone distributing it with a written offer on how to get it; > in that case you can just "redistribute" that written offer... See > http://www.gnu.org/copyleft/gpl-faq.html#WhatDoesWrittenOfferValid and item 3 > in the GPL. > > Now, I'm not 100% what "a written offer" means; does the README that comes with > cdrdao, containing a link to the sourceforge site, constitute "a written offer" > on how to get the source code? In that case you can just add that to your site. > > The cdrdao source code isn't that large, so the easiest way is just to put > those on your site, too. (If you also distribute the windows binaries you also > have to provide the cygwin source code, and that is quite large IIRC). > > > > -- > Jonas Munsin <jm...@ik...> KeyID: 1024/98A0C47D > PGP Key fingerprint 9F 69 9D 96 80 DD 8E D0 D8 A0 30 66 F9 55 63 B4 > Debian GNU/Linux | PhD student @ Embedded Systems Lab / TUCS |
From: Free S. F. <lic...@gn...> - 2002-07-17 15:52:39
|
[Please forgive our delay, but lic...@gn... and gn...@gn... are highly backlogged.] On Fri, May 03, 2002 at 09:07:20PM +0300, Jonas Munsin wrote: > Hello, > > I am CC:ing this to gn...@gn..., maybe someone there has time to clarify if a > README file constitutes "a written offer" (see my third pharagraph bellow). > > On Thu, May 02, 2002 at 04:32:46PM +0100, morrison wrote: > > My program just builds a command line and executes the compiled cdrdao > > binary . The binaries are to be distributed with my program so I guess I > > just have to supply the user with the means to get the source by way of > > posting them on my site or linking to the cdrdao soundforge site. > > Linking to the cdrdao sourceforge site isn't enough, I think. If you provide > the binaries, you have to accompany the source or a written offer on how to > obtain the source, unless you distribute the unmodified binaries noncomercially > and got it from someone distributing it with a written offer on how to get it; > in that case you can just "redistribute" that written offer... See > http://www.gnu.org/copyleft/gpl-faq.html#WhatDoesWrittenOfferValid and item 3 > in the GPL. > > Now, I'm not 100% what "a written offer" means; does the README that comes with > cdrdao, containing a link to the sourceforge site, constitute "a written offer" > on how to get the source code? In that case you can just add that to your site. > > The cdrdao source code isn't that large, so the easiest way is just to put > those on your site, too. (If you also distribute the windows binaries you also > have to provide the cygwin source code, and that is quite large IIRC). > > > > -- > Jonas Munsin <jm...@ik...> KeyID: 1024/98A0C47D > PGP Key fingerprint 9F 69 9D 96 80 DD 8E D0 D8 A0 30 66 F9 55 63 B4 > Debian GNU/Linux | PhD student @ Embedded Systems Lab / TUCS There are two points I will make that I think will make this clear. 1) When you distribute only binaries of something that is GPL'd, you need to provide the user receiving the binaries with a means to receive the source in a medium similar to how the user received the binaries. So, if they downloaded them off your website, they need to be able to receive the source off your website. If you distribute them on a physical medium (CD, etc.), they must be able to receive the source via mail order in a physical medium. 2) The written offer given with the binaries must specify how the user can obtain the source. If the binaries on a website, the written offer must specify where on the website to get the source. The offer on CDs must specify how the user can write to the distributor to obtain the source via mail order. Note, it is not enough for a third party distributor to point to the origin site of the GPL'd source, they must provide them on their own site (see http://www.gnu.org/licenses/gpl-faq.html#SourceAndBinaryOnDifferentSites for details) Hope this helps, Dan -- Dan Tomalesky Licensing Question Volunteer Free Software Foundation This is not legal advice. If you need legal advice, consult a lawyer. |
From: burnatonce <bur...@nt...> - 2002-07-18 18:41:04
|
Thanks for your answer Dan. Your attachment and the faq item linked clears thing up nicely. Source is currently availiable on my site but may have to be moved to a friends webspace in the future so the following: "However, if you make arrangements with another site to keep the necessary source code available, and put a link or cross-reference to the source code next to the binaries, we think that qualifies as "from the same place". " was nice to see! :) Jamie. ----- Original Message ----- From: "Free Software Foundation" <lic...@gn...> To: "Jonas Munsin" <jm...@ik...> Cc: "morrison" <mor...@pu...>; <cdr...@li...>; <lic...@gn...> Sent: Wednesday, July 17, 2002 4:55 PM Subject: Re: [Cdrdao-devel] Regarding GPL compliance |