This file is the net layer API for the MySQL client/server protocol, which is a tightly coupled, proprietary protocol owned by MySQL AB. Any re-implementations of this protocol must also be under GPL, unless one has got an license from MySQL AB stating otherwise.
I am second to few in being a fan and a proponent of the GPL. However, this claim in this comment is utterly bogus. It dates back to willful misunderstanding and FUD spreading and the desire to strong-arm the sale of licenses on the part some people at the old MySQL AB company.
If license of source code followed network protocol of running implementation (which stretches "derived work" to an extent even an RIAA flack dare not even dream), then it would be illegal to view a web page served from IIS from Firefox.
And besides, the MySQL client server protocol is not even "owned" by MySQL AB. It's very directly merely extended (and not very much) from the old MSQL client server protocol.
To moot the entire issue, the new libdrizzle client protocol library not only speaks the new different and superior Drizzle client/server protocol, it also speaks the old MySQL protocol. The license for libdrizzle is BSD.
This whole thing makes me annoyed, because this kind of overreach and FUD just makes the GPL itself look bad.
For what it's worth:
ReplyDeletekostja@bodhi:/opt/local/work/bk/mysql-4.1/sql$ bk annotate net_serv.cc | grep -5 prop
monty 1.30 along with this program; if not, write to the Free Software
monty 1.30 Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA */
monty 1.1
monty 1.41 /*
monty 1.55 This file is the net layer API for the MySQL client/server protocol,
monty 1.55 which is a tightly coupled, proprietary protocol owned by MySQL AB.
monty 1.55 Any re-implementations of this protocol must also be under GPL
monty 1.55 unless one has got an license from MySQL AB stating otherwise.
monty 1.55 */
monty 1.55
monty 1.55 /*
Quite so.
ReplyDeleteLooks like an oversight to me, not malice. It should have been removed when the web pages were updated.
ReplyDeletehttp://bugs.mysql.com/bug.php?id=52107 - I expect this fragment to vanish soon.