Handling master/stable package differences on CI

[Martin Gräßlin]

On Wednesday 04 March 2015 09:16:39 Andreas Cord-Landwehr wrote:
> Hey, currently we have different sets of packages available for master and
> for stable branch groups on build.kde.org. Most prominent among them, only
> master branches can build against Qt5.4, but not stable ones (only
> providing Qt5.3). As a more or less result of this, after the branching of
> Applications 15.04, the new stable branch of Rocs started to fail building
> as it requires Qt5.4.
> 
> I am writing this mail mostly as I am unsure how to proceed here, in
> particular with the 15.04 Beta-1 release being close in front of us.
> 
> What I currently see:
> * Rocs has a hard dependency to Qt5.4 for a reason (since it uses the
> QtQuick Statemachine) and would require considerable code changes to make
> it work with Qt5.3 (well, a "hack" to get it building on build.k.o is
> possible with only requiring Qt5.3, since building and unit tests should
> pass, yet IMO that sends a very wrong message to packagers as the
> application would fail starting when built against Qt5.3)

Suggestion:
ifdef properly for usage with Qt 5.3 so that it builds on the CI. But bind it 
to a CMake variable which gets passed to the build on the CI system. Something 
like
-DIKNOWTHATITWILLBREAKWITHQT53

The same problem will btw hit Plasma once we branch. KWin is hard depending on 
Qt 5.4 and I think Eike introduced some hard 5.4 dependencies in other areas, 
too.

Cheers
Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/release-team/attachments/20150304/cecf1533/attachment.sig>