<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Dec 10, 2014 at 2:27 PM, René J.V. <span dir="ltr"><<a href="mailto:rjvbertin@gmail.com" target="_blank">rjvbertin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">>> The thing is, if ever we want to allow Qt4 and Qt5 to be present at the same time, the installation location will *have* to change, and dependent ports will have to comply with that.<br>
><br>
>Yes, but not by using variants. MacPorts doesn't have the capability to declare a dependency on a variant (ticket #126) and I'm still not convinced that that should ever change.<br></span></blockquote></div><br>How about a main port with the new paths, and a stub port or subport that depends on the main port, conflicts with qt4-mac, and installs the symlinks? Then we can replace qt4-mac with the stub port at some point. (Maybe make the stub port qt4-mac-devel, so it's maybe already handled as a potential dependency *and* it's announcing that it will eventually replace qt4-mac.)<br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div><div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div></div>
</div></div>