Qt 4.6 conflicts with upcoming Maemo5 releases?
 

I've recently seen this service message in many applications's testing pages in Extras Testing:

What does that mean? I've already installed Qt 4.6 (as dependencies of many Extras-Testing apps), will I have problems with upcoming firmware upgrades? Should I remove them?

P.S.: sorry if I'm talking nonsense ;)

Re: Qt 4.6 conflicts with upcoming Maemo5 releases?
 

I don't know if he posted here or not but from the maemo developers mailing list

Re: Qt 4.6 conflicts with upcoming Maemo5 releases?
 

Yeah, already know that (I've posted a link to that in my first post...), but it doesn't answer my questions.

Re: Qt 4.6 conflicts with upcoming Maemo5 releases?
 

I don't think there'll be any issues, no. The Qt4.6 packages in the update will have a higher version number and will therefore simply replace the old ones.

Removing the Qt4.5 packages is more likely to cause the issues, as any installed applications making use of these will also need to be uninstalled (or updated with a Qt4.6 version). This is an issue Nokia will be well-aware of though, and presumably have a cunning plan to deal with.

Re: Qt 4.6 conflicts with upcoming Maemo5 releases?
 

It is not that simple as it will mean that the name of the qt packages will have to change. Which in turn can break application dependencies. I'm still unsure how the upgrade will go and how many packages will (not) be broken by it.

Re: Qt 4.6 conflicts with upcoming Maemo5 releases?
 

Why does the name have to change?

Re: Qt 4.6 conflicts with upcoming Maemo5 releases?
 

Moving this thread to the Development forum. The integration of the official Qt 4.6 in a Maemo 5 update is something that should bring the attention of the developers affected but, in principle, shouldn't bother end users at all. The magic should happen behind the scenes for them.

Yes, the Qt & maemo developers are working on that "cunning plan". I'm definitely not the expert on the matter but I'll make sure they are aware of this thread and the one in maemo-developers.

Re: Qt 4.6 conflicts with upcoming Maemo5 releases?
 

On behalf of the end-users, thank you. And thanks to all the developers for whom this will make more work and more headaches. Please, please know how much we end-users appreciate you.

Re: Qt 4.6 conflicts with upcoming Maemo5 releases?
 

Thanks qgil. I hope that it will not bother end users at all, but I'm a little worried.
Maybe those who have not installed Qt 4.6 yet (because it's in Extras-Testing) will not have troubles, but what about me and those who have installed the testing one?

Re: Qt 4.6 conflicts with upcoming Maemo5 releases?
 

We know what to do because extras testing is extras testing and if you have problems with it, then make bug report and reflash. Simple as that.

Re: Qt 4.6 conflicts with upcoming Maemo5 releases?
 

Hi,

Same issue here, can't send my app to autobuilder due do broken dep it seem. Was building fine two days ago

Fabrice

Re: Qt 4.6 conflicts with upcoming Maemo5 releases?
 

How did I not think about it? ;) Simple as hell.
:D

Re: Qt 4.6 conflicts with upcoming Maemo5 releases?
 

Not nonsense at all.

The Qt4.6 libraries in extras-devel and now -testing are optified, i.e. they reside in the /opt directory. The final Qt4.6 libraries will not be in /opt, so this is more about preventing a lot of people having Qt4.6 libraries in two places.
Also the devel libraries are named 'wrong' to avoid the name collusion with the current Qt4.5 libraries.

On top of that the people working with Qt objected to the idea that their work in progress would be promoted to extras. They want to make it good and final and then get it out properly.

As for firmware upgrade, no problems there. Even if you have the devel libraries on device, the upgrade will go through fine. You just end up with two copies of the libraries, then it is time to remove the devel versions (once the packages that depend on them are changed to depend on the final Qt version).

I hope that was somewhat clear :)

Re: Qt 4.6 conflicts with upcoming Maemo5 releases?
 

As the Qt4.6 libraries are not API or ABI compatible with the Qt 4.5 libraries, then I would have thought that a different name was a necessity anyway, otherwise incompatible applications will still be installable.