Changes between Version 272 and Version 273 of SummerOfCode

Timestamp:

Mar 8, 2017, 11:04:19 PM (8 years ago)

Author:

neverpanic (Clemens Lang)

Comment:

Add some more detail to the migration task

SummerOfCode

@@ -106 +106 @@
 Currently when MacPorts users upgrade to a new OS or hardware they are advised to follow a set of manual [https://trac.macports.org/wiki/Migration migration instructions]. These instructions can be challenging for casual users to follow and in some cases more difficult if executed after the OS upgrade or hardware change.
 
-The goal of the new port migrate action is to automate the processes described in the migration documentation.
+The goal of the new port migrate action is to automate the processes described in the migration documentation. The steps to migrate would be roughly:
+
+1. Rebuild MacPorts itself (e.g. by invoking selfupdate) if it has not been rebuilt for the new OS already. MacPorts has a version field compiled in that allows tracking this.
+2. Store a copy of all installed ports with their variants so the same exact set can be re-installed.
+3. Deactivate all installed ports.
+4. Re-install all ports from the stored list of ports. Properly deal with interruptions and resuming so that failures during this procedure can be separately debugged and the migration re-attempted.
 
 * Difficulty: Medium