On Thursday, 2 January 2020 21:10:46 -03 Ville Voutilainen wrote: > > Ok, you're talking about the fact that linking to a GPL'ed library makes a > > derivative work, according to the FSF, and therefore the plugin is GPL > > too. > > I've heard lawyers interpret this differently, but the only opinion that > > matters here is that of the lawyer representing the entity that is doing > > the hosting and publishing. > > I'm talking about what you wrote, which is > "So the current MySQL > maintainers (Oracle) made the choice for us by not allowing us to ship the > plugin." > > They didn't make the choice for us, and they didn't disallow us to > ship the plugin. > We chose not to ship it.
Indeed. I had misunderstood why we couldn't/wouldn't ship the plugin. I had thought that the licensing of MySQL had changed considerably since the MariaDB split and we weren't allowed to ship a derivative work at all. Thanks for clarifying it's actually plain, ol' GPL and it's our choice. > > This gets solved by linking to the LGPL equivalent. That's > > libmariadb.so.3. > > Yes, we can ship a mariadb plugin in any package we like, perfectly in > accordance with our current > packaging policy. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel System Software Products _______________________________________________ Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
