On Tue 16 Apr 2013 11:53:34 Joey Hess escribió:
> Lisandro Damián Nicanor Pérez Meyer wrote:
> > Hi Joey! With both Qt4 and Qt5 in the archive we will need a
> > transition for the buildsystem. In order to avoid FTBFSes of
> > packages that currently build OK, I've created this small patch.
> >
> > + # Select Qt4 by default except if overriden otherwise.
> > + if (!$ENV{QT_SELECT}) {
> > + push @options, "-qt=qt4";
> > + }
>
> Is this doing something different than would be done if building with
> --buildsystem=qmake_qt4 ?I must admit that I didn't know about qmake_qt4. But even if it is no difference, the current problem now is to do a smooth transition to allow Qt4 and Qt5 to coexist without breaking existing packages. The current idea makes qt4 the default (we do not have qt5 packages in the archive now) until we get the transition sorted: - Setting an environment variable to let qtchooser (new upstream app) select between qt4 or qt5 - Using qmake_qtx, if that's a posibility. - B-D on libqtx-default Once sorted, we remove that variable. > If I set this option, how do I ever migrate away from it without > rendering every package that uses Qt4 insta-buggy? We are preparing to go ahead with a transition which we will propose as a release goal for Jessie. The patch above helps us with a smoother transition. Kinds regards, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
signature.asc
Description: This is a digitally signed message part.
