Sune Vuorela [[email protected]] > I have, as a distributor, frequently gotten 'hate' in #qt for providing > switchable qmakes.
> And from a 'user support' PoV, having to write "depending on what you > have set as your default you can maybe write qmake, maybe you need to > oither switch the default to qt5 or alternatively write qmake5 to > build things" is a much longer sentence than > > "write qmake5 to build things". > > The advantage of doing it upstream, rather than having me to do it, > kevin to do it, will to do it, jonathan to do it, ... is that > - the implementation is the same > - the result is the same > - you do not have to consider what distribution teh user is on when > trying to help in #qt, on interest@ or in forums. just write 'use > qmake5 That's achievable by a few lines of text: Linux distributors are strongly advised to install all Qt 5 related executables (qmake, uic, rcc, ...) with unmodified names to a directory that is not in $PATH and set up symlinks 'qmake5' etc that are in $PATH. Linux distributors are strongly advised to install all Qt 4 related executables (qmake, uic, rcc, ...) with unmodified names to a _different_ directory that is not in $PATH and set up symlinks 'qmake4' etc that are in $PATH. If Linux distributors feel strong about it, they may use their distributions "native" system to handle alternatives to set up 'qmake' etc links in the path to point to the qmake binary in either the Qt 4 or the Qt 5 binaries directory, [Suggesting to modify PATH is probably the saner choice, I don't really care about this part] User support could then be: "write qmake5 to build Qt 5 things" Users/Admins could then use the distribution's "defaults" system to switch the "system" Qt version, they can also override the system setup by modifying their local PATH settings, per-shell even. None of these operations are "unusual", or "technically challenging", or "cumbersome", and it does not require, or even only benefit, from the proposed renaming of the binaries. Andre' _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
