Handling master/stable package differences on CI
Albert Astals Cid
aacid at kde.org
Thu Mar 5 19:24:45 UTC 2015
El Dijous, 5 de març de 2015, a les 15:05:47, Andreas Cord-Landwehr va
> On Wednesday 04 March 2015 09:33:11 Martin Gräßlin wrote:
> > 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
> > to a CMake variable which gets passed to the build on the CI system.
> > like
> > -DIKNOWTHATITWILLBREAKWITHQT53
> Sounds fine to me, I will do this tonight if nobody objects.
How do you plan to do that? I mean CI can't pass
-DIKNOWTHATITWILLBREAKWITHQT53 to your cmake.
Also, not sure what's the point of a CI that is compiling something that's not
really "the code" but it's something else, sure I know I've been strict on
stuff compiling on CI, but isn't it worse to compile "fake code" than to not
compile (and wait until we use a newer Qt in stable)?
> release-team mailing list
> release-team at kde.org
More information about the release-team