On Sunday, October 21, 2012 12:56:05 Konstantin Ritt wrote: > >> > Why not use a tool of a new name? Why overload the meaning and > >> > responsiblity of qmake? > > > > <snip> > > If the new tool is to be installed to /usr/bin/qmake and the Qt 4 qmake is > > today at /usr/bin/qmake, packagers have to change everything in their Qt 4 > > packages or they will conflict and not be coinstallable. I thought that > > was > > the main reason for this whole thing. If you covered that in your initial > > email, I missed it. > > The packagers have to change the only Qt4 qmake's name/path and
The whole point of this proposal used to be to make it not necessary for distros to patch Qt. This proposal as you state is requires everyone to patch Qt 4 even more (Right?). This is exactly why this point should have been part of the initial proposal: If we don't care about distros patching Qt 4 anymore - only Qt 5 - that is a particular goal, but I haven't seen it stated like that anywhere. I didn't know that was the goal in particular of this new proposal. Thanks, -- Stephen Kelly <stephen.ke...@kdab.com> | Software Engineer KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company www.kdab.com || Germany +49-30-521325470 || Sweden (HQ) +46-563-540090 KDAB - Qt Experts - Platform-Independent Software Solutions ** Qt Developer Conference: http://qtconference.kdab.com/ **
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
