<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font face="Times New Roman">Re-sending to have the message go to
the list:<br>
</font></p>
<p><font face="Times New Roman">Hello all,</font></p>
<p><font face="Times New Roman">As a long-time user of MacPorts,
I've migrated a few times a memory from one of those times was
how disastrously poorly the migration went. Be it my fault in
following the directions or a problem with my setup, I ended up
hard-uninstalling everything and reinstalling ports from
memory/as I re-discovered needing them. Since then, I have
actively sought out this set of instructions. My edits were to
bring the instructions into a proactive position, knowing that
the installed ports need to be logged and reinstalled, versus a
reactive position, having MacPorts not work and direct you to
the wiki page.</font></p>
<p><font face="Times New Roman">Better documenting on the Migration
wiki page to express the full context of the instructions would
be useful. It may also be valuable to include at least a link to
the Migration page as an "Uncommon Tasks" relative to <a
class="moz-txt-link-freetext"
href="https://guide.macports.org/chunked/using.common-tasks.html">https://guide.macports.org/chunked/using.common-tasks.html</a>
. This would give users more exposure to the process *before*
they ever needed to use it rather than discovering additional
effort as (some?) ports are broken and MacPorts requires a full
reinstall to get a functioning system back.<br>
</font></p>
<p><font face="Times New Roman">Of course, it would be best if
MacPorts could handle the majority of the OS-change work and the
documentation was almost as short as "Upgrade OS, run `sudo port
<some upgrade task>`, and let everything reinstall."</font></p>
<p><font face="Times New Roman">Meanwhile, while writing this email,
I found an additional deficiency in the current process in which
re-setting the requested status doesn't work reliably. I look
forward to continuing to improve the documentation once the
overall structure of this page is decided on.<br>
</font></p>
<div class="moz-signature">Thomas R. Murphy (<a
class="moz-txt-link-abbreviated"
href="mailto:thomas.russell.murphy@case.edu">thomas.russell.murphy@case.edu</a>,
<a class="moz-txt-link-abbreviated" href="mailto:trm70@case.edu">trm70@case.edu</a>)<br>
GPG Key ID: 959D48BF<br>
</div>
<div class="moz-cite-prefix">On 2017-08-29 12:09:14, Umesh Singla
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAK2-mZFyJZLx8TGjF81iq69Fq-XovjN1MBc_M_jQQW1NRx4rEg@mail.gmail.com">
<div dir="ltr">Hi
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Aug 29, 2017 at 8:30 PM,
Rainer Müller <span dir="ltr"><<a
href="mailto:raimue@macports.org" target="_blank"
moz-do-not-send="true">raimue@macports.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex"><span class="gmail-">On
2017-08-29 16:41, Arno Hautala wrote:<br>
> Just as a message is sent to the user list when a
new MacPorts version<br>
> is posted, a message could be sent when a new OS is
released that<br>
> reminds users that migration will be required.<br>
<br>
</span>Such a message would probably only reach a small
amount of users...<br>
<br>
Before we discuss more workarounds, I still see no reason
why it would<br>
be required to run these steps before upgrading the OS.
Otherwise I<br>
would prefer to go back to the old order of steps that
always work and<br>
are less confusing.</blockquote>
<div><br>
</div>
<div>Following the use case which it serves currently, I
agree that it is best to go with the original sequence of
steps. Probably, <span style="font-size:12.8px">thomasrussellmurphy
reinstalled the complete OS and the guide didn't serve
his purpose.</span></div>
<div><span style="font-size:12.8px"><br>
</span></div>
<div><span style="font-size:12.8px">- Umesh</span></div>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>