As far as I recall, GPL3 closed the loophole on the specific case that Naveen outlined, as this was considered not in the spirit of GPL2. People were using remote connections get around the concept of binary linking. I only read one of the early drafts, not sure if that was in the final.
On Fri, Jun 25, 2010 at 1:53 PM, Anton Persson <don.juan...@gmail.com>wrote: > Well, to connect to a MySQL database you need a connector, and the > connector library shipped with MySQL is under GPL. Which is what I meant. > And, hence, corporations buy licenses from MySQL to avoid having to release > their applications under the GPL. (If you still don't believe me, try > explaining the reason why they HAVE a dual license model... If they only > wanted to sell support and indemnification, a separate paid-for license > would NOT be needed... See Red Hat for an example of how that works..) > > And; the INTENT of MySQL is that if you use the GPL version of the MySQL > database, your application should also be GPL. But, of course, there are > loopholes. However, using these loopholes in a way that is obviously a > "circumvention" is against this INTENT. > > If you want people to respect YOUR intellectual property, you should > respect others as well, and not exploit their software in an unintended > manner. > > Regards > Anton > > > On Fri, Jun 25, 2010 at 10:04 PM, Fabrizio Giudici < > fabrizio.giud...@tidalwave.it> wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 6/25/10 04:55 , Andy Savage wrote: >> > I forgot to say in my previous post. >> > >> > In response to the person talking about MySQL. I believe this is >> > quite different as MySQL is a completely self contained database >> > system that other applications communicate with. As in, it's a >> > completely GPL package, rather than a part of another application. >> > >> > If you actually incorporated the MySQL code within your application >> > I believe it would break GPL (presuming your application was closed >> > source). I am not sure how this applies to the MySQL libraries that >> > are setup to use mysql say from PHP. >> > >> >> This is correct, and I was referring to MySQL. The difference stays in >> that "incorporating" - as you said, if the two apps were still >> considered as two separate, collaborating apps it would be fine. >> >> On 6/25/10 09:39 , Anton Persson wrote: >> > Not entirely true. Yes; a LOT of non-FLOSS (closed source) apps use >> MySQL.. But they do that by buying the non-FLOSS-licenses that MySQL >> _sell_. >> > MySQL allows you to use MySQL with the GPL license as long as YOUR >> application is also using GPL. That is their idea, and that's why many >> prefer PostgreSQL. So, if you are using MySQL with the GPL license you >> are doing something MySQL doesn't want you to do. >> >> >> This is COMPLETELY incorrect. Corporates buy the paid license of MySQL >> because of support and indemnification. The GPL license CLEARLY says >> that a GPL application can be used without applying the virality when >> it runs in a separate process and is used by connecting with a socket >> (or other ways, such as clear API access points - otherwise, >> everything using Linux should be GPL as well, and clearly it isn't). >> >> >> - -- >> Fabrizio Giudici - Java Architect, Project Manager >> Tidalwave s.a.s. - "We make Java work. Everywhere." >> java.net/blog/fabriziogiudici - www.tidalwave.it/people >> fabrizio.giud...@tidalwave.it >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG/MacGPG2 v2.0.14 (Darwin) >> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ >> >> iEYEARECAAYFAkwlC9oACgkQeDweFqgUGxd1sgCgkmJuBWeEGzc50aATw08v/Uke >> Is0AoJ/o8RAoJ1XMTRvlWXQA3jM74sHQ >> =Q5fR >> -----END PGP SIGNATURE----- >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Android Developers" group. >> To post to this group, send email to android-developers@googlegroups.com >> To unsubscribe from this group, send email to >> android-developers+unsubscr...@googlegroups.com<android-developers%2bunsubscr...@googlegroups.com> >> For more options, visit this group at >> http://groups.google.com/group/android-developers?hl=en >> > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com<android-developers%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Shane Isbell (Founder of ZappMarket) http://twitter.com/sisbell http://twitter.com/zappstore http://zappmarket.com -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
