On Sunday 17 June 2007 13:12:41 Peter Eisentraut wrote: > That isn't the point. The problem is that just calling "qmake" is useless > because either it's a Qt 3 package, which won't work if qmake is the Qt 4 > version, or vice versa. It's perfectly OK to have both qmake-qt3 and > qmake-qt4 available, but the alternative should be removed because it > cannot be useful.
The big point is here that very many upstream build systems are expecting a 'qmake' command to be available. (and similar for moc, uic and others) It generally gives 3 possibilities. 1) have people fix all their packages to use the -qt3 or -qt4 version. (that would probably break quite some things. These packages needs proper build-conflicts. 2) have both qt4 and qt3 ship /usr/bin/qmake (and others) and declare appropriate conflicts. 3) Use alternatives as it is currently. Of these possibilities, the least evil one is the one we are currently using - option 3 with alternatives. This is why this isn't considered as a bug, but as the only way to make it work. /Sune -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
