Bartosz Fabianowski schrieb: >> because some of the qt4 ports *will* conflict with qt3 and thus KDE 3, >> in particular the qt4 tools such as moc, uic and qmake > > I am using a Kubuntu machine for some uni-related work and they have Qt > 3 and Qt 4 coexisting nicely there. Of course, this means that Qt 4's > tools had to be renamed, to stuff like qmake-qt4. Would this be too much > of a mess to maintain on FreeBSD?
Yes. Unlike things like autotools (or anything that uses autoconf as a buildsystem) Qt has zero support pre- or suffixing its tools by itself (i.e. you cannot tell its buildsystem to install them this way) and qmake has no support for generating Makefiles with calls to such non-standard binaries either, nor does it parse environment variables which could be used to point to such tools, meaning that every single port that uses Qt4 would need heavy patching to make this sort of thing work (at least, that's what I've found while investigating this - feel free to correct me if I got it wrong, I sure would like make them coexist). We simply don't have the resources to do that. The problem isn't really new either - the changeover from qt2 to qt3 was just as bad, and since both qt2 and qt3 were monolithic ports, they were conflicting completely (back then, we had our own home-made version of the CONFLICTS feature in bsd.kde.mk just to deal with this). Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org
signature.asc
Description: OpenPGP digital signature
_______________________________________________ kde-freebsd mailing list [email protected] http://freebsd.kde.org/mailman/listinfo/kde-freebsd
