es from Qt 5.15 into dev, around RC time (end of April) and
> once the .0 release is packaged. So no changes will be lost.
Please disable merging only after 5.14 branch is closed, so all changes to it
make it into 5.15.0.
The 5.14 branch closes the moment 5.15.0-rc1 is out.
--
Thiago Macieira
like
macros. But since we don't like to break users' code bases any more than the
standard does, it needs to be a process over a couple of releases.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
___
Reader::supportedImageFormats() is documented as requiring
> QApplication, but I do not know whether that is relevant here.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
___
Development mailing
ect to get a reply?
Yes.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
On Friday, 13 March 2020 04:19:22 EST Konstantin Tokarev wrote:
> 13.03.2020, 08:55, "Thiago Macieira" :
> > For a complex set of needs like Qt's, you'l still need a dedicated person
> > or multiple people. And this isn't free either, despite there being a lot
> &
On Friday, 13 March 2020 04:48:21 EST Florian Bruhin wrote:
> On Thu, Mar 12, 2020 at 10:51:31PM -0700, Thiago Macieira wrote:
> > I also need two CIs so I can test on just three OSes.
>
> Can you elaborate on that? I assume those are Linux, macOS and Windows?
Correct.
> Pret
ons you still can get an idea of overall progress of build,
> while in Coin you just have to wait with fingers crossed.
https://testresults.qt.io/coin/
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
__
ied
into the QScopeGuard object before C++17 and mandatory copy elision. That
functor should not throw when being copied, much less when moving.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
___
Developm
rchestration.
Please note this is not just wild guessing. I am looking into this very topic
(GitHub repositories, CI, etc.) as part of my work inside Intel.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
__
ck as resolving the PR ?
I doubt it. It doesn't recognise when I do that manually. It only recognises
when GitHub itself dos the rebase prior to application. All other cases, the
PR needs to be closed as if it got rejected.
--
Thiago Macieira - thiago.macieira
having some modules switch wholesale from our CI and from
Gerrit to GitHub, using whatever review mechanism and CI can be obtained with
GitHub, while other modules remain with Gerrit+Coin.
Why would we do that?
--
Thiago Macieira - thiago.macieira (AT) int
On Thursday, 5 March 2020 07:29:07 PST Bogdan Vatra via Development wrote:
> În ziua de joi, 5 martie 2020, la 17:21:11 EET, Thiago Macieira a scris:
> > On Thursday, 5 March 2020 07:14:44 PST Vitaly Fanaskov wrote:
> > > I think something like std::expected is a
have QSystemResult in QtCore already. This predates both std::expected and
Result from Rust.
One of my abandoned commits (see the I/O thread) was an update to it to make
it better.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Archit
On Friday, 28 February 2020 10:42:54 PST Thiago Macieira wrote:
> On Thursday, 27 February 2020 11:50:02 PST Simon Hausmann wrote:
> > Hi,
> >
> > Declarative in 5.15 (5.14?) has public API taking a std::function and that
> > appears to be okay so far :)
>
> Goo
On Friday, 28 February 2020 12:12:35 PST Matthew Woehlke wrote:
> On 28/02/2020 13.39, Thiago Macieira wrote:
> > That's my point: it's a reasonable feature to ask that any good IDE
> > implement.
> It may be reasonable to ask *an IDE* to implement such a feature. It is
> *n
on-type template
parameter.
But it can't be retrofitted without BC break to existing signals, since the
function name is already used.
The signal emission would be different:
qEmit(::bytesWritten, count);
or
qEmit(q->bytesWritten(), count);
--
Thiago Macieira - thiago.macieira (AT)
.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
QTBUG-74102
https://codereview.qt-project.org/212258
https://codereview.qt-project.org/212259
https://codereview.qt-project.org/212260
https://codereview.qt-project.org/212261
https://codereview.qt-project.org/212262
https://codereview.qt-project.org/212263
--
Thiago Macieira - thiago.macieira
ing on a non-insignificant
platform: MinGW (at least some builds of it). I just hope that people using
those platforms simply hadn't skipped qtdeclarative in 5.14.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Softw
ion being called is code in
this project, another project, or is generated during the build.
Whether the feature will be implemented is a whole other story. But it's
reasonable to ask.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
_
f it's a member of the class, it can't be added
or removed without changing the class's size and layout, so it would tie our
hands for future improvements.
You'd see instead:
this->emptied().emit(...);
connect(foo, foo->emptied(), ...);
--
Thiago Macieira - thiago.macieira (AT)
for attributes that the user intended to write.
[[declare_attribute(qt::emit)]];
later:
[[qt::emit]] closed();
This is a standard change. Alternatively, [[gnu::declare_attribute(qt::emit)]]
until C++23.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - In
tePreeditText
updatePreviewWidget
UpdateProperty
updateRequest
updates
uploadProgress
urlSelected
urlsSelected
viewportEntered
visibilityRequest
wantData
widgetRemoved
windowActivated
workAreaResized
The ones starting with a capital letter seem to be standardised D-Bus
interfaces.
--
Thiago Macieira - thi
o the wrong places.
>
> You seem to assume everyone used QtCreator as their IDE of choice. That is
> not a reasonable assumption I think.
It is a reasonable feature request for ALL IDEs to understand what a Qt signal
is.
--
Thiago Macieira - thiago.macieira (AT) intel.com
onnection slot connected. I don't think the functionality was
hooked up after BlockingQueuedConnection was added, but it cannot work with
regular QueuedConnection.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software
On Monday, 24 February 2020 03:07:00 PST Lars Knoll wrote:
> > On 21 Feb 2020, at 18:49, Thiago Macieira
> > wrote:
> > On Friday, 21 February 2020 08:39:57 PST Volker Hilsheimer wrote:
> >
> >> I’m fine with that, and as communicated by Jani, deprec
der class.
The reason we added it was because we needed and the Standard Library
equivalent isn't (wasn't) available in all platforms Qt needed to be compiled
on.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software
On Friday, 21 February 2020 08:53:33 PST Oswald Buddenhagen wrote:
> On Fri, Feb 21, 2020 at 08:29:54AM -0800, Thiago Macieira wrote:
> >can we deprecate setupChildProcess() in Qt 5.15 and *remove it* in 6.0?
>
> at least, we should. ;)
> but let's bikeshed the name of the call
flip side of the coin: adding a new API to replace the overriding.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
___
Development mailing list
Development@qt-project.org
https://lists.qt-pr
ts to warn if the
project doesn't declare keywords or no_keywords. Allow that to stay for 2 or 3
years so projects do update to declare their choices. This can start right
now, in 5.15.
At some point after that, change the default. Like, for example, in Qt 7.
--
Thiago Macieira - thiago.m
On Friday, 21 February 2020 04:59:02 PST Ville Voutilainen wrote:
> Having a keyword-extension to normal C++ is ugly as sin, to some of
> us. It causes
> fair amounts of "wtf is that?".
That was my reaction when I first saw it, in 1999.
Over 20 years later, I don't bat
On Friday, 21 February 2020 03:21:32 PST Ville Voutilainen wrote:
> Yes, and the name change was discussed but rejected.
Do you know why it was such strong against? Was it, "darn it's too late" or
was it "we don't care"?
--
Thiago Macieira - thiago.macieira (AT) intel.c
On Tuesday, 18 February 2020 15:44:24 PST Thiago Macieira wrote:
> $ grep -r 'public QProcess'
> kcoreaddons/src/lib/io/kprocess.h:class KCOREADDONS_EXPORT KProcess : public
> QProcess
> khtml/src/java/kjavaprocess.h:class KJavaProcess : public QProcess //QObject
> kpty/src
omium sources we use.
b) Spectre (one of the two or both) also affects AMD and ARM and every single
out-of-order processor system out there. Please see the technical docs for
more information.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel
4.1.exe) [1]
Okay, but what version of Qt is the Qt Installer using? Installer team, can
you check?
Also, anyone affected, PLEASE upgrade your BIOS right now. Your system is
insecure. (or buy Intel)
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software
On Tuesday, 18 February 2020 03:17:38 PST Edward Welbourne wrote:
> Thiago Macieira (17 February 2020 20:35) wrote:
> > Sorry, this just occurred to me. This is a request for 5.15 feature freeze
> > exception.
> >
> > Re: https://bugreports.qt.io/browse/QTBUG-17331
&g
you want to run code. It will
clean up your code and QProcess's. And if we like it, we can have a flag
saying "my function is async-signal-safe too", which will allow the
optimisations and the use code.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel
urces and cache the
artefacts in our own CI systems.
I'm fine with that. I just need to figure out where the artefact storage for
GitHub Actions is...
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
uest to my project.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
ng
reviewed?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
> Does this sound like a more reasonable approach?
The problem is that new API may still be interacting with QObject pointers. Do
you propose using Daniel's classes for transferring ownership (reparenting) or
indicating a non-owning transfer for those too?
--
Thiago Macieira - thiago.macieir
of cleaner API over time,
without the feature freeze exception and potential standard library
compatibility issue, but makes us keep using FORKFD_USE_FORK for other
derivation reasons.
Opinions?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Sof
On Sunday, 16 February 2020 10:30:41 PST Thiago Macieira wrote:
> Is there a volunteer to help figuring this out? I'm strapped for time and
> access to the 2017 compiler is limited for me.
Alternative: drop support for MSVC 2017. It is known to have a serious
variable initialisation regr
ing this out? I'm strapped for time and
access to the 2017 compiler is limited for me.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
as a second shot across the bows (after namespace
> boost::signals) that we should change something.
Orthogonal to your request: can we ask C++20 to change the name of this
function? We've been #define'ing emit for nearly 30 years.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Sof
On Tuesday, 28 January 2020 19:31:34 PST Thiago Macieira wrote:
> On Tuesday, 28 January 2020 03:52:49 PST Tino Pyssysalo wrote:
> > It is also possible to transfer the qtaccount.ini file to a CI machine,
> > which removes the need for manual/interactive login. The qtaccou
)
It's probably very related. Let me see if I can modify one of our examples to
cause this problem.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
___
Development mailing list
Development
On Thursday, 13 February 2020 09:53:11 PST Thiago Macieira wrote:
> I can confirm krdc is affected just the same way that KMail and VirtualBox
> are: it works on screen 1, but fails to repaint on screen 2.
>
> It's a much simpler application than KMail to debug. I can reproduce thi
On Tuesday, 28 January 2020 19:14:50 PST Thiago Macieira wrote:
> I don't know what makes KMail different. I thought it was the use of a
> qtwebengine window, but the qtwebengine examples seem to work fine.
>
> My current theory is embedding of X11 content
> (QWidget::createWindo
libraries that most benefit from it (QtCore, QtGui and Qt3D).
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
chievable.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
al and a getter) in 5.15 and dev.
We wanted to do it for 5.6, so 6.0 seems like early enough, yes.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
___
Development mailing list
Development@qt-pr
eplacement or if the API is actually harmful.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
On Wednesday, 5 February 2020 09:41:58 PST Alexander Akulich wrote:
> On Wed, Feb 5, 2020 at 6:58 PM Thiago Macieira
>
> wrote:
> > The correct signal for an error situation is errorOccurred, like in
> > QLocalSocket and QProcess.
>
> Actually both QLocalSocket
ention in Qt. I thought that the same
> convention is to use '-ed' verbs in signal names.
It is. The correct signal for an error situation is errorOccurred, like in
QLocalSocket and QProcess.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System So
d to 5.15 for
6.0 to be ready was in place, before sending the feature freeze announcement?
Anyway, how are we on Qt 6.0 future-compat features? Are they in 5.15?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
_
subscribing. More likely,
these emails are from dummy accounts.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
Right, the patch applies but there's no vulnerability to be mitigated in the
first place. The issue was introduced in 5.12.0 with the search for "haswell/"
plugins.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
_
I think a reasonable attack scenario remains if the plugin does not exist in
> the system.
You're talking about an application that attempts to load an optional plugin
with no pathname?
I didn't test that. I don't know if LoadLibrary() searches $PWD at all. I only
tested non-optional plugi
is outside Qt's scope. But the case of linear arrangement
of screens can be solved. The only questions are whether it's necessary to
solve it to get the currently-broken applications fixed and if it is, how to
detect the cases where we can and when to give up.
--
Thiago Macieira - thiago.ma
QLibrary will find the actual plugin later and will load that. The worst that
could happen is that the interposing DLL has valid but incorrect metadata
causing another DLL to be loaded that shouldn't be. This other DLL isn't under
the control of the attacker, though and neither is the name of th
applications to load
and execute malicious code. This issue was verified on Linux and probably
affects all Unix operating systems, other than macOS (Darwin). This issue does
not affect Windows.
Patch: https://code.qt.io/cgit/qt/qtbase.git/commit/?
id=e6f1fde24f77f63fb16b2df239f82a89d2bf05dd
--
Thiago
On Wednesday, 29 January 2020 16:55:18 PST Thiago Macieira wrote:
> That's because we're sloppy and haven't done a proper job. The security
> advisory was supposed to go out at the same time as the Qt 5.14.1 release
> announcement. But the release announcement went out without the
ut
very few people have an idea of what that is about.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
clearly. The difference is, of course,
that the Qt Company has far more developers who can look after the areas
maintained by the rest of the community than the community has to look after
areas maintained by the Qt Company.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel
[1] note how the binary downloads don't use them due to DLL hell and other
issues. I really recommend rebuilding everything from sources for your
official releases.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel
as it is, there's one other: the incentive of a licence that doesn't
have the TiVo clause.
> In conclusion a 400 euro per developer/year is a nice spot for converting
> most LGPL users to Commercial.
Conclusion based on opinion, not data. Sorry, this is not how it works.
--
Thiago Maci
On Wednesday, 29 January 2020 01:09:25 PST Nicolas Arnaud-Cormos via
Development wrote:
> Hi Thiago,
>
> On 29/01/2020 04:25, Thiago Macieira wrote:
> > The source code on download.qt.io remains anonymously accessible.
>
> How do you know that?
> What would prevent
On Tuesday, 28 January 2020 21:03:49 PST André Somers wrote:
> On 29/01/2020 04:27, Thiago Macieira wrote:
> > So you're advocating being acquired by a bigger company that has a
> > different business and regards Qt only as a means to an end?
> >
> > Can you spell &qu
> avoid having companies moving from OS to commercial just before release,
> but you also do not want to discourage fair usage of OS (including some
> prototyping as far as I'm concerned).
It's not. It's a negotiation with The Qt Company.
--
Thiago Macieira - thiago.macieira (AT) intel
based
applications on Windows with GitHub Actions, right?
Downloading during build is an absolute no-go.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
___
Development mailing list
Development@q
On Tuesday, 28 January 2020 02:07:00 PST NIkolai Marchenko wrote:
> There will be no offline installer for non paying people. That is the
> hurdle. Did you even read the actual blog post?
No. I assumed the relevant information was in both places.
--
Thiago Macieira - thiago.ma
one of those behind CMake?)
So you're advocating being acquired by a bigger company that has a different
business and regards Qt only as a means to an end?
Can you spell "Nokia" ?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Sy
onymously accessible.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
Source version and then, before releasing, go buy the commercial version.
Just buy the commercial licence upfront, or release as Open Source.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Pr
e painted again on the left.
I don't know what makes KMail different. I thought it was the use of a
qtwebengine window, but the qtwebengine examples seem to work fine.
My current theory is embedding of X11 content (QWidget::createWindowContainer,
use of QWindow::fromWinId, etc.). Which exampl
ose releases (that's pretty much QtC people today)
c) bug triaging in those releases (again, mostly QtC people anyway)
d) applying of security fixes, if any (in addition to the Open Source
releases)
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Softw
On Monday, 27 January 2020 22:37:47 PST Benjamin TERRIER wrote:
> You might have missed the info because it is in the blog post, but not in
> Lars email:
>
> There will be no more open source offline installer.
Thanks, I stand corrected.
--
Thiago Macieira - thiago.macieira (A
On segunda-feira, 27 de janeiro de 2020 15:16:35 PST Kevin Kofler wrote:
> Thiago Macieira wrote:
> > All security fixes are made available to everyone, for all Qt versions
> > that they affect, provided it's still a supported Qt version
> > (or it was easy to ma
On segunda-feira, 27 de janeiro de 2020 14:30:56 PST Giuseppe D'Angelo via
Development wrote:
> Il 27/01/20 22:52, Thiago Macieira ha scritto:
> > All security fixes are made available to everyone, for all Qt versions
> > that
> > they affect, provided it's still a
e installer from another
machine, then copied it over to the VM, and installed there.
Now you're going to download the offline installer from another machine after
typing your password, then copy over to the VM and install there.
What's the hurdle?
--
Thiago Macieira - thiago.macieira (AT) intel.
alignment on a Qt LTS. If that's confirmed, it would
be the first, after 4 years of having LTS releases.
So it's completely understandable to have concluded that the LTS releases
weren't useful to Linux distributions.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Int
made available to everyone, for all Qt versions that
they affect, provided it's still a supported Qt version (or it was easy to
make the fix).
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
ficial answer)
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
o receive it and there is
> no way for him to push it there.
Nothing changes there. All patches for security can be published for all
branches. Those patches are often attached to the security announcement email.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Softw
filed https://bugreports.qt.io/browse/QTBUG-81695, but I'm reporting here
because this issue affects kmail majorly in 5.14 and thus makes it VERY
difficult for me to work. Please consider this bug a P0.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software
ng the former
> as a typedef. Leave the qApp macro as-is but deprecated. Add the
> qCoreApp and qWidgetApp macros (analogous to qGuiApp)
I prefer (A), possibly also deprecating the macro entirely.
--
Thiago Macieira - thiago.macieira (AT) intel.c
?
BTW, what is the situation on Apple platforms these days? I remember something
about not having "_debug" in pure debug builds either.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System S
to the change. As a
maintainer, I can't ignore the "ping" and will review, though it may take me a
few more days to find the time.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
___
Development m
as to integrate, which may happen
> to be quite difficult given the problem we have to synchronize all
> modules). Then hopefully there is no further problem.
I don't think there's a way out of this just yet.
I'll modify my patches to work with C++14.
--
Thiago Macieira - thiago.macieira (AT)
C++17 as absent, so we wouldn't try to use the aligning operator new.
The reason for my failure is that the Standard Library is not as new as the
compiler itself. We do not have C++17 standard library.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Pr
of trivial fixes that made most of it work, but we ran into at least one
compiler bug (fixed in later versions of GCC) and a problem with templates.
Those aren't fixed and won't be.
So saying GCC 4.8 isn't supported and wasn't supported in 5.14.0 is correct.
--
Thiago Macieira - thiago.macieir
On Wednesday, 8 January 2020 14:12:17 PST Olivier Goffart wrote:
> On 08.01.20 18:21, Thiago Macieira wrote:
> > qcc doesn't seem to support it.
> >
> > kernel/qcoreapplication.cpp: In static member function 'static void
>
> Not yet:
>
> - qmake isn't build
I wonder what happens to debug-and-release builds now.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org
off.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
lugin 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
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
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
> >
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 Sys
ly, 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.
Make it difficult for people to use your software and they won't.
--
Thiago Macieira - thiago.macieira (AT) intel.com
So
f the two you want, meaning the one that needs to be
present at runtime? If so, my recommendation stands: use MariaDB.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
___
Development mailing l
801 - 900 of 6026 matches
Mail list logo
