Changes between Version 52 and Version 53 of Migration
- Timestamp:
- Jun 10, 2012, 6:01:30 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Migration
v52 v53 36 36 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`. 37 37 38 === Automatically reinstall ports (EXPERIMENTAL)=== #automatic38 === Automatically reinstall ports === #automatic 39 39 40 A script has been written to automate Step 4 above, though it is still experimental. If it fails, you will just have to do it manually. (But see workaround for conflicting ports below.)40 A script has been written to automate Step 4 above, though it has some caveats. If it fails, you will just have to do it manually. (But see workaround for conflicting ports below.) 41 41 42 42 To use it, you will first need to run steps 1-3 as described above. Then: … … 49 49 50 50 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. 51 52 The requested status of the ports will also not be preserved, since it is not available to the script. You can restore it manually by doing something like this (where myport1, myport2 etc. are the ports you actually asked for): 53 {{{ 54 sudo port unsetrequested installed 55 sudo port setrequested myport1 myport2 … 56 }}}