<br>
What's the recommended series of command lines for that?<br><br>
Thanks!<br>
Darren<br><br><div class="gmail_quote">On Tue, Jun 9, 2009 at 8:19 AM, Joshua Root <span dir="ltr"><<a href="mailto:jmr@macports.org">jmr@macports.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On 2009-6-9 22:15, Tim Visher wrote:<br>
> Hi Darren,<br>
><br>
> On Tue, Jun 9, 2009 at 1:20 AM, Darren Weber<<a href="mailto:dweber@macports.org">dweber@macports.org</a>> wrote:<br>
>> What happens to a MacPorts installation when we install a distribution<br>
>> upgrade to OSX, say Leopard to Snow Leopard? Do we need to backup the<br>
>> MacPorts installation, or is the ${prefix} path immune to the upgrade? What<br>
>> about startup items (launchd or anything that violates the mtree)?<br>
><br>
> I can't be sure technically but I've upgraded OS X for every release<br>
> since MacPorts came out (Back when it was called DarwinPorts. Jaguar?)<br>
> and I've never had to reinstall it. So, anecdotally I think you're<br>
> safe. If you care very deeply you should of course back it up just in<br>
> case.<br>
<br>
</div>Both MacPorts base and each port are built for a specific major OS<br>
version. Maybe they'll work acceptably on a newer version, maybe they<br>
won't. The only safe option has always been to record your installed<br>
ports, uninstall MacPorts entirely, install the correct base version for<br>
your OS, then install your ports again.<br>
<br>
- Josh<br>
</blockquote></div><br>