[Interest] Qt Maintenance Tool vs Online Installer

Koehne Kai Kai.Koehne at digia.com
Sat Feb 15 22:14:58 CET 2014

>From: interest-bounces+kai.koehne=digia.com at qt-project.org [interest-bounces+kai.koehne=digia.com at qt->project.org] on behalf of Alan Ezust [alan.ezust at gmail.com]


>I wanted to update from Qt 5.2.0 to Qt 5.2.1 on Linux.


>I ran MaintenanceTool and it spent about 3 minutes contacting the server before it told me it had to update

itself. Then it did, it restarted, spent another 3 minutes looking for updates, and the told me I had one for QtCreator. But no update for Qt.

>So I let it update QtCreator. 


>Then I downloaded a newer online installer (linux) and ran that to install Qt 5.2.1.

>It won't let me un-check qtcreator even though I just updated it. 

Every installation of the Qt SDK is "self-contained" - that is, if you install the Qt SDK twice in different directories they don't know about each other (which is sometimes, but not always, exactly what you want). And since Qt Creator is a mandatory part of the SDK installation you'll end up with multiple versions of it.

> It also won't let me install Qt 5.2.1 right next to Qt 5.2,  (my previous install location was /usr/loca 
> /Trolltech) so I am forced to choose a different directory, and download the latest QtCreator again!


> The Maintenance tool great for updating qtcreator but what's the point if you always have to download  
> qtcreator again each time you get a newer Qt?

You don't have to do that always. However, newer Qt versions sometimes require also a newer version of Qt Creator ... I'm not sure that is the case with Qt 5.2.1 / Qt Creator 3.0.1 though, will check the dependencies on Monday.

> And why can't the online installer be a maintenance tool and let you install updates?

The maintenance tool is the online installer after it has been installed. If you re-run the original installer you're starting a new, independent installation of Qt ...

I can see how this can be confusing. Maybe the installer should be able to somehow find already existing installations, and warn the user about it / let it run the respective maintenance tool. If you agree you might file a feature request at bugreports.qt-project.org?



More information about the Interest mailing list