<div dir="ltr">Supported or not...this way seemed to work for a majority of my ports and I was wondering whether nuking all 459 of my ports for the sake of a few that don't work seems like an inefficient solution. It seems there are other ways to approach this problem...</div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Oct 19, 2014 at 2:30 PM, Chris Jones <span dir="ltr"><<a href="mailto:jonesc@hep.phy.cam.ac.uk" target="_blank">jonesc@hep.phy.cam.ac.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
<br>
<br>
<br>
> On 19 Oct 2014, at 7:26 pm, Lawrence Velázquez <<a href="mailto:larryv@macports.org">larryv@macports.org</a>> wrote:<br>
><br>
>> On Oct 19, 2014, at 12:57 PM, Chris Jones <<a href="mailto:jonesc@hep.phy.cam.ac.uk">jonesc@hep.phy.cam.ac.uk</a>> wrote:<br>
>><br>
>> I still think something went wrong and some memory of your previous OSX 10.9 installations is still present. I cannot see how you would get messages regarding Darwin 13 otherwise.<br>
><br>
> It seems that Carlo successfully upgraded all his other ports, and the ones he listed are the ones that failed for one reason or another. Since they are left over from Mavericks, base considers them outdated.<br>
<br>
</div></div>My understanding though is this is not a supported way of upgrading after an OS upgrade. Removing all ports first then reinstalling those you want is the recommendation.<br>
<br>
><br>
> vq<br>
</blockquote></div><br></div>