Changes between Version 110 and Version 111 of Migration
- Timestamp:
- Oct 14, 2019, 9:47:19 PM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Migration
v110 v111 1 = Migrating MacPorts after major operating system upgrade or from one computer to another =1 = Migrating MacPorts after a major operating system upgrade or from one computer to another = 2 2 3 3 A MacPorts installation is designed to work with a particular operating system and a particular hardware architecture. … … 11 11 12 12 13 Note: If you move from on Mac to another mac using [https://en.wikipedia.org/wiki/Migration_Assistant_(Apple) Migration Assistant], you have to do it first.13 Note: If you move from one Mac to another Mac using [https://en.wikipedia.org/wiki/Migration_Assistant_(Apple) Migration Assistant], you have to do it first. 14 14 15 15 == Migration procedure == 16 16 17 17 18 1. [=#xcode **Install the latest version of Xcode and the Xcode command 18 1. [=#xcode **Install the latest version of Xcode and the Xcode command-line tools**] 19 19 20 20 Update the development tools by … … 65 65 xargs sudo port setrequested < requested.txt 66 66 }}} 67 Warning: if a port in `requested.txt` was ''not'' installed in the previous step, the iterative `setrequested` will terminate, leaving some ports still marked as not-requested. Edit `requested.txt` to remove any ports that were not installed and repeat this step. Double 67 Warning: if a port in `requested.txt` was ''not'' installed in the previous step, the iterative `setrequested` will terminate, leaving some ports still marked as not-requested. Edit `requested.txt` to remove any ports that were not installed and repeat this step. Double-check your desired ports are set as requested with `port echo requested`. 68 68 69 69 == Troubleshooting == 70 70 71 Though it is now quite well-tested, the restore_ports script may fail in some cases. One known issue is that the script will fail if there are conflicting ports in the list. It's possible to have conflicting ports installed provided at most one of the conflicting set is active. If the script fails for this reason, you can delete one of the conflicting ports from myports.txt and then simply run the script again. You may need to do this multiple times if there are multiple conflicting ports listed.71 Though it is now quite well-tested, the restore_ports script may fail in some cases. One known issue is that the script will fail if there are conflicting ports in the list. It's possible to have conflicting ports installed provided at most one of the conflicting set is active. If the script fails, for this reason, you can delete one of the conflicting ports from myports.txt and then simply run the script again. You may need to do this multiple times if there are multiple conflicting ports listed. 72 72 73 73 In the worst case, you can reinstall your ports manually by browsing `myports.txt` and installing the ports one by one, remembering to specify the appropriate variants: … … 75 75 sudo port install portname +variant1 +variant2 … 76 76 }}} 77 Note that if you have specified variants which are not the default, you may need to install ports in an order other than the alphabetical order recorded in `myports.txt`. You may skip explicitly installing ports that you did not request as long as they are not using non-default variants ,since they will be installed as dependencies of other ports.77 Note that if you have specified variants which are not the default, you may need to install ports in an order other than the alphabetical order recorded in `myports.txt`. You may skip explicitly installing ports that you did not request as long as they are not using non-default variants since they will be installed as dependencies of other ports. 78 78 79 79 If things go really wrong, don't forget that you can always [https://guide.macports.org/chunked/installing.macports.uninstalling.html uninstall MacPorts] entirely before manually reinstalling ports.