#13640: qt4-mac conflicts with qt3 on /opt/local/bin/lrelease ----------------------------------+----------------------------------------- Reporter: vinc17@macports.org | Owner: blair@macports.org Type: defect | Status: new Priority: High | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: ----------------------------------+----------------------------------------- Comment (by blair@macports.org): What name do you suggest for lrelease to? How would this work if you only need lrelease on qt3? None of our projects are on qt4, so I don't want to break qt3. Maybe we can write a shell script that is /opt/local/bin/lrelease and finds the latest installed lreleaseN, say lrelease3 for qt3, lrelease4 for qt4. We would have an qt-lrelease package for the shell script that both qt3-mac and qt4-mac depend upon. This sounds like the alternative system for Debian, maybe we should look at adding something like this to MacPorts. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/13640#comment:2> MacPorts </projects/macports> Ports system for Mac OS

#13640: qt4-mac conflicts with qt3 on /opt/local/bin/lrelease ----------------------------------+----------------------------------------- Reporter: vinc17@macports.org | Owner: blair@macports.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: Qt tools; select ----------------------------------+----------------------------------------- Comment (by blair@macports.org): I don't have the cycles to make the new qttools_select package, write the script that selects the correct lrelease binary, renames lrelease in both qt3-mac and qt4-mac. I would review patches to get this done though. Regards, Blair -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/13640#comment:6> MacPorts </projects/macports> Ports system for Mac OS