Bug#363150: closed by Sune Vuorela <[EMAIL PROTECTED]> (qmake, uic, moc and others as alternatives)
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]
Bug#363150: closed by Sune Vuorela <[EMAIL PROTECTED]> (qmake, uic, moc and others as alternatives)
On Sun, Jun 17, 2007 at 01:12:41PM +0200, Peter Eisentraut wrote: > Am Sonntag, 17. Juni 2007 12:09 schrieb Debian Bug Tracking System: > > We currently don't consider this a bug, but a feature to actually have both > > qt versions installable. > > > > if you want to be completely sure which one you use, you can either set > > PATH and/or QTDIR appropriately. > > 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. You are right that 'qmake', as an alternative either pointing to version 3 or version 4, is useless when called from a script (eg. from debian/rules). But as a shortcut when used manually, it's perfectly fine IMHO. What about documenting that scripts should use qmake-qt3 or qmake-qt4, and make it a bug if a build script calls qmake? Jan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#363150: closed by Sune Vuorela <[EMAIL PROTECTED]> (qmake, uic, moc and others as alternatives)
reopen 363150 reopen 409953 stop Am Sonntag, 17. Juni 2007 12:09 schrieb Debian Bug Tracking System: > We currently don't consider this a bug, but a feature to actually have both > qt versions installable. > > if you want to be completely sure which one you use, you can either set > PATH and/or QTDIR appropriately. 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. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
