<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Sep 9, 2014 at 10:12 AM, Daniel J. Luke <span dir="ltr"><<a href="mailto:dluke@geeklair.net" target="_blank">dluke@geeklair.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":26y" class="a3s" style="overflow:hidden">It's not entirely obvious what the 'correct' behavior would be, though.<br>
<br>
Your new omniORBpy (upgraded with -u) is the only one available after the upgrade. The installed openmodelica-devel is now broken (won't work with the new omniORBpy). rev-upgrade /could/ ignore the -u and build a new openmodelica-devel to fix the issue for you, but you wouldn't be able to re-activate the old one and have it work.<br>
<br>
I would suggest that what you actually want to be doing is something like:<br>
<br>
port upgrade outdated<br>
port uninstall inactive and not openmodelica-devel (and maybe using one or more of the pseudo-portname selectors to also hang on to any old dependencies or dependents).<br></div></blockquote></div><br>I was wondering if the right thing to do is create local ports of the old versions, possibly modified to install in separate places so they can all be concurrently active. This would also allow rev-upgrade to rebuild the old version against the new dependencies. (But does not address the problem of old versions not being compatible with newer versions of dependencies; this isn't really a simply solvable case.)<br clear="all"><div><br></div>-- <br><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>