On 23/02/12 12:12, David Greaves wrote: > We need to plan how Mer can include Qt5 > > Mika Bostrom and Marko Helenius have been working on the packaging. > > This is a fairly significant change and we need to figure out how to handle > phasing it into core. > > Please yell if you have a significant interest and can't make that time. > > David > Minutes (rather sparse) are here: http://mer.bfst.de/meetings/mer-meeting/2012/mer-meeting.2012-02-27-09.30.html and there's a link to the full logs.
Some highlights: Qt4 is currently the default 'qt' in Mer, with qt5 co-existing and applications able to build against it by specifying it directly long term co-existence tbd. 4.8 can be supported in reverse way of how we allow qt5 to co-exist for the time being, all the packages belonging to qt5 have been prefixed with "qt5-" in any case, meaning that the package requirements will be explicit qt has a releasing@ mailing list which qt5 maintainer should be on -- and we should sync with whatever naming they come up with for qt5 based rpm systems, such as QtOnPi, as to make it easier to transfer source packaging across distributions Have an OBS project (Mer:Qt5) on community OBS where we have the packaging in it at first, with a goal to start including it into mer core (by 12/March) Have a Qt5 page with useful links like those here http://wiki.merproject.org/wiki/Category:About and other pages with Mer-specific Qt5 information Packaging and tarballs are modularised now We'll have a sync meeting on 5/March We will use the current Qt5 snapshot until our packaging works, possibly taking a peek upstream and cherry picking if we think there's a solution to be found then after that we re-sync There are some issues with a few packages like: qtquick1, qt3d, qttools and qtwayland David -- "Don't worry, you'll be fine; I saw it work in a cartoon once..."
