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
On Thu, 2 Jan 2020 at 22:12, Thiago Macieira wrote:
>
> On Thursday, 2 January 2020 10:45:28 -03 Ville Voutilainen wrote:
> > On Thu, 2 Jan 2020 at 13:35, Thiago Macieira
> wrote:
> > > On Monday, 30 December 2019 18:03:04 -03 Ville Voutilainen wrote:
> > > > We have the same licensing in Qt as
On Thursday, 2 January 2020 10:45:28 -03 Ville Voutilainen wrote:
> On Thu, 2 Jan 2020 at 13:35, Thiago Macieira
wrote:
> > On Monday, 30 December 2019 18:03:04 -03 Ville Voutilainen wrote:
> > > We have the same licensing in Qt as MySQL does, for all practical
> > > purposes.
> >
> > Qt is
On Thu, 2 Jan 2020 at 13:35, Thiago Macieira wrote:
>
> On Monday, 30 December 2019 18:03:04 -03 Ville Voutilainen wrote:
> > We have the same licensing in Qt as MySQL does, for all practical purposes.
>
> Qt is freely redistributable, in source or binary forms.
As is GPLed MySQL. We don't
On Monday, 30 December 2019 18:03:04 -03 Ville Voutilainen wrote:
> We have the same licensing in Qt as MySQL does, for all practical purposes.
Qt is freely redistributable, in source or binary forms.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System
On Mon, 30 Dec 2019 at 20:56, Thiago Macieira wrote:
> we ship with. For all I care, it has won the battle. And most importantly, we
> *can* ship that plugin while we can't ship the other. So the current MySQL
> maintainers (Oracle) made the choice for us by not allowing us to ship the
> plugin.
On Monday, 30 December 2019 12:45:40 -03 Christian Ehrlicher wrote:
> And on windows it's currently not possible to link against mariadb since
> the (import) libs are named libmariadb.
Why? Why can't they provide a copy of the file with the different name? It's
not like the name of the file
Am 30.12.2019 um 16:52 schrieb Kevin Kofler:
Current Qt 5 (and I presume and hope, Qt 6) just works as shipped, i.e., it
can be built against current MariaDB libraries without any patches.
With this patch also on Windows:
https://codereview.qt-project.org/c/qt/qtbase/+/285384
A separate
Thiago Macieira wrote:
> Can you explain why this isn't done now? Why can't we build against the
> MariaDB libraries and ship those, with their ability to connect to MySQL
> servers?
FYI, this is exactly what Fedora (and I think also several other
distributions) are already doing.
Even legacy
Am 30.12.2019 um 15:13 schrieb Thiago Macieira:
- do we need a small paragraph in the documentation why we can't ship
it anymore and that MariaDB should be preferred?
Yes. Just ship the MariaDB one.
Can you explain why this isn't done now?
Maybe since nobody cares? Don't know. That's why I
On Monday, 30 December 2019 10:38:59 -03 Christian Ehrlicher wrote:
> - do we want to have a separate plugin for MariaDB?
No. The plugin code is the same and the application code using the plugin is
the same. There's no need for two plugins. One must suffice.
> - do we need to split the
Hi,
due to the fact that the pre-built MYSQL plugin can no longer be shipped
with the Qt installer we get a lot of questions in the forum why it's
not shipped anymore and how to build this driver from the sources. We
already tried to improve the documentation for it but it's not an ideal
12 matches
Mail list logo
