On Sunday 20 March 2016 17:23:44 Eric Valette wrote: [snip] > True but on the otehr hand you could rebuild the offending packages > specifically for experimental using qt 4.6 dependencies. Because as it > is you let the user with the choice of not updating or building the > packages themselves... That would also mean that the KDE maintainer will not be able to push a new version of KDE to experimental. As we use experimental to do the initial work of packaging both Qt and KDE I'm afraid it's not that easy to do that. Except you mix new versions of Qt and KDE... sounds like a recipe for mayhem. And rebuilding the whole KDE stuff also means putting more pressure to the release team, which already has enough in it's plate. So I'm afraid that as long as applications use Qt's private headers we do not have any other better choice. -- “If you want to finish university, you should take care about getting on with the teachers. The result are submissive citizens that won’t face authority even if they know they’re right, in order to avoid problems“ Miriam Ruiz, http://www.miriamruiz.es/weblog/?p=187 Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
Attachment:
signature.asc
Description: This is a digitally signed message part.