Package: qt3-dev-tools Version: 3:3.3.6-1 Severity: normal Currently, qmake is an alternative that points to either qmake-qt3 or qmake-qt4 depending on administrator preference. But we have dozens of packages in the archive that simply call "qmake" to build, and that is going to lead to failures if someone ever decides to change that alternative locally: Apparently, trying to build Qt3 packages using qmake-qt4 and vice versa leads to a hard failure.
We could place the burden on those packages to fix their rules, but that seems to be the wrong place in my mind. Generally, handling non-interactive "file processing" (build) tools through the alternatives systems is a problem. We don't do it with gcc, we don't do it with python, we do it with java and that causes all sorts of problems. With qmake, it seems totally wrong because these programs don't do the same thing: one works and one just fails. What might work is a wrapper script like autoconf has, that looks at the sources and decides which version to call. I can't offer any advice on how to detect the right version, but maybe someone has an idea. Alternatively, one version should be the default qmake and there needs to be a transition sometime. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
