Re: [ossig] CA open-sources Ingres database - News & Technology -CNETAsia

[Dinesh Nair <dinesh@xxxxxxxxxxxx>]

On Thu, 27 May 2004, Kenneth Wong wrote:

> However, it is likely that connection via TCP sockets is safe, otherwise
> our entire networking infrastructure needs a serious look at.  In that

let's not overgeneralize. FSF isnt trying to outlaw TCP sockets. what
they're saying is that creative uses of TCP sockets in order to try to
split a program into two (GPL and non-GPL) is not in the spirit of this.
once again, their usage of "initimate enough" bears some harder
definition.

> Now the client library that connects via sockets to the GPL MySQL server
> would probably have to be non-GPL. There are several options for this,

the reality of it is, the mysql client library (as issued by mysql ab) is
in two forms, commercial license and gpl. if you're linking against the
gpl (note, not lgpl) version of the mysql libraries, then your code has
to be gpl.

a workaround is what you've provided below:
>
> including using the older, LGPL libraries or reverse engineering your
> own libraries from scratch. Either way, you can use the GPL'ed MySQL
> server with your proprietary app. Whether you want to or not is a

and what happens when mysql ab changes the client<-->server comms protocol
? i.e older clients compiled with out-of-date libraries wont work anymore
for the latest greatest feature sets ?

(this has happenned at least once before in mysql's history, i remember
having to recompile some app binaries because i upgraded the mysql server
and needed to use the newer set of libraries they provided because the
older ones wouldnt connect to the server)

using the older libraries or rolling your own is workable as long as
you're happy with the feature sets provided with that version. the moment
they add new features you want to use in newer versions, you're in a
little bit of a bind.

> The FSF will now say all software using GPLv3 can't even be communicated
> with using sockets? Right. Sure. Then it'll be 100% GPL Internet or
> nothing. I seriously don't think so.

well, they're considering this. see
http://www.gnu.org/licenses/gpl-faq.html#UnreleasedMods

this specifically covers ISPs/ASPs who use a modified GPL program to
provide a service to the public.

and once again, they're not trying to ban sockets. they're trying to
define "intimate enough" such that those that try to creatively split a
program using sockets or any other IPC would be clear on when the other
part needs to be GPL and isnt.

> Besides which, even if the FSF produces GPLv3, the current users of GPL
> do not have to upgrade the license to GPLv3. It's at their discretion

no, they don't. however, what if the principal project authors do, say
linus releasing kernel 3.2 under GPLv3 ? (i know, using the kernel as an
analogy for the client-server thing is not apt, but you get the picture)

> pay up. Not "if you want to be non-GPL, pay up". FUD. Thanks, MySQL, for
> perpetuating it.

well, like i said, i'm believing that this is more towards a language
issue rather than anything intentional.

Regards,                           /\_/\   "All dogs go to heaven."
dinesh@alphaque.com                (0 0)    http://www.alphaque.com/
+==========================----oOO--(_)--OOo----==========================+
| for a in past present future; do                                        |
|   for b in clients employers associates relatives neighbours pets; do   |
|   echo "The opinions here in no way reflect the opinions of my $a $b."  |
| done; done                                                              |
+=========================================================================+


---------------------------------------------------------
To unsubscribe: send mail to ossig-request@mncc.com.my
with "unsubscribe ossig" in the body of the message