Tim Uckun wrote:

> If I write an application that uses these drivers it
> would not obligate me to GPL my code (even though the drivers may
> themselves be GPLed). You are only subject to license if your code is
> somehow a derivative of a GPLed code.

That's not my understanding. I'm trying to be helpful, to let you know
that GPL does not mean what you think it means. But it's up to you.
Just don't say we didn't warn you when MySQL AB comes to take your
application. ;-)

Here are some clues:

[http://www.mysql.com/information/index.html]
"MySQL uses the GPL (GNU General Public License) http://www.gnu.org, to
define what You may and may not do with the software in different
situations. If you feel uncomfortable with the GPL or need to embed
MySQL into a commercial application you can buy a commercially licensed
version from us."

[http://www.gnu.org/copyleft/gpl.html]
"If your program is a subroutine library, you may consider it more
useful to permit linking proprietary applications with the library. If
this is what you want to do, use the GNU Library General Public License
instead of this License."

> I seriously doubt that once a code is GPLed it
> can be un GPLed.

Perl, for example, uses two different license schemes. Perl is
distributed explicitly stating that one can use _either_ the GNU GPL or
the "Artistic License" which is a Perl-specific license. They state
that users can choose which license suits them.

It should be just as possible to apply two different license schemes to
MySQL, one which is GPL, and one which is non-GPL but is only granted to
people who give money to MySQL AB. Licenses can also be non-perpetual,
etc.

Regards,
Bill Karwin