Changes between Version 98 and Version 99 of Migration

Timestamp:

Aug 28, 2017, 11:57:16 PM (7 years ago)

Author:

thomasrussellmurphy (Thomas Russell Murphy)

Comment:

Change procedure to have the preparation step of logging installed ports *before* installing the new OS and upgrading MacPorts

Migration

@@ -12 +12 @@
 == Migration procedure ==
 
-1. [=#xcode **Install the latest version of Xcode and the Xcode command line tools**]
-
-   After a major system change, update the development tools by
-   [https://guide.macports.org/#installing.xcode installing the latest version of Xcode].
-   Open the Xcode application once after installation and follow any prompts.
-   Install the command line tools package as well.
-
-2. [=#base **Reinstall MacPorts base**]
-
-   After updating the development tools,
-   [https://www.macports.org/install.php install the base MacPorts system]
-   for your new platform, either from the appropriate installer or from
-   source.
-
-   **Update macports.conf**: If your {{{macports.conf}}} (typically at {{{ /opt/local/etc/macports/macports.conf}}}) contains uncommented settings for {{{universal_archs}}} or {{{build_arch}}}, you will likely want to update them, since unlike earlier OS versions, the compiler on Snow Leopard and later will build for x86_64 by default on systems that support it. The default values will be fine for almost all users, so unless you know you need something different, just comment out these two lines. Several other settings in {{{macports.conf}}} have changed their defaults over the years. Take a moment to compare each line of your {{{macports.conf}}} with the corresponding line in {{{macports.conf.default}}} in the same directory. Unless you know a reason why a line in your settings file should be different from the defaults, adopt the line from the defaults file.
-
-3. [=#ports **Reinstall ports**]
+1. [=#preparation **Prepare for system version upgrade**]
    a. Save the list of installed ports:
       {{{
@@ -45 +29 @@
       sudo rm -rf /opt/local/var/macports/build/*
       }}}
+
+2. [=#osupgrade **Install new OS**]
+
+   Perform your OS upgrade.
+
+3. [=#xcode **Install the latest version of Xcode and the Xcode command line tools**]
+
+   After a major system change, update the development tools by
+   [https://guide.macports.org/#installing.xcode installing the latest version of Xcode].
+   Open the Xcode application once after installation and follow any prompts.
+   Install the command line tools package as well.
+
+4. [=#base **Reinstall MacPorts base**]
+
+   After updating the development tools,
+   [https://www.macports.org/install.php install the base MacPorts system]
+   for your new platform, either from the appropriate installer or from
+   source.
+
+   **Update macports.conf**: If your {{{macports.conf}}} (typically at {{{ /opt/local/etc/macports/macports.conf}}}) contains uncommented settings for {{{universal_archs}}} or {{{build_arch}}}, you will likely want to update them, since unlike earlier OS versions, the compiler on Snow Leopard and later will build for x86_64 by default on systems that support it. The default values will be fine for almost all users, so unless you know you need something different, just comment out these two lines. Several other settings in {{{macports.conf}}} have changed their defaults over the years. Take a moment to compare each line of your {{{macports.conf}}} with the corresponding line in {{{macports.conf.default}}} in the same directory. Unless you know a reason why a line in your settings file should be different from the defaults, adopt the line from the defaults file.
+
+5. [=#ports **Reinstall ports**]
    a. Download and execute the restore_ports script. (If you installed MacPorts from source and used a custom prefix, then you'll need to use the -p option when you run restore_ports.tcl; see `./restore_ports.tcl -h`.)
       {{{
@@ -58 +64 @@
       xargs sudo port setrequested < requested.txt
       }}}
+
+   You can now safely remove the `myports.txt` and `requested.txt` documents and the `restore_ports.tcl` script.
 
 == Troubleshooting ==