Changes between Version 28 and Version 29 of Migration

Timestamp:

Apr 20, 2010, 10:02:08 PM (15 years ago)

Author:

dweber@…

Comment:

--

Migration

@@ -48 +48 @@
 === Convert myports.txt into an install script (EXPERIMENTAL) === #sed_script
 
-These sed scripts will get close to coverting myports.txt into an installation script.  It will not arrange the order of the installation according to the dependency tree and it cannot check the most recent variants against those of the installed ports.  It will strip away any variants with '+darwin*', '+macosx' or '+i386', because any platform or architecture variants should be determined automatically.  The {{{myports.bash}}} file should be reviewed carefully and the variant specifications should be compared with the output from {{{port variants <aPort>}}}.  Some ports may have a long list of +variant options, but they might all be replaced with a {{{+huge}}} variant.  Also look for duplicate ports with different versions, some of them might not be required (e.g., docbook-xml-*).
+These sed scripts will get close to coverting myports.txt into an installation script.  It will not arrange the order of the installation according to the dependency tree and it cannot check the most recent variants against those of the installed ports.  It will strip away any variants with '+darwin*', '+macosx' or '+i386', because any platform or architecture variants should be determined automatically.  The {{{myports.bash}}} file should be reviewed carefully and the variant specifications should be compared with the output from {{{port variants <aPort>}}}.  Some ports may have a long list of +variant options, but they might all be replaced with a {{{+huge}}} variant.  Also look for duplicate ports with different versions, some of them might not be required (e.g., {{{docbook-xml-*}}}).
 
-The {{{'&& \'}}} at the end of each command line will effectively create one long command line, with contingent installation of successive ports; should any one port install fail, no others will run (e.g., try {{{ls abc.txt && cat abc.txt}}} where no file abc.txt exists).  When any one of the ports fails to install, the {{{myports.bash}}} script can be edited to remove all the prior ports that are already installed.
+The following will output {{{myports.bash}}} with {{{'&& \'}}} at the end of each command line.  This will effectively create one long command line, with contingent installation of successive ports.  Should any one port fail to install, no others will run (e.g., try {{{ls abc.txt && cat abc.txt}}} in a directory where no file exists called {{{abc.txt}}}).  When a port fails to install, the {{{myports.bash}}} script can be edited to remove all the prior ports that are already installed.
 
 {{{
@@ -71 +71 @@
 }}}
 
-This is another possibility, which will list all the ports on one {{{sudo port install}}} command, rather than a separate command for each port.  In a perfect world (ha! ha! ha!), this port command might resolve the dependency tree and arrange the correct installation order, but don't hold your breath for that ;-)
+This is another possibility, which will list all the ports on one {{{sudo port install}}} command, rather than a separate command for each port.
 
 {{{