[MacPorts] Migration modified

[Rainer Müller]

What is the purpose of this example? Is it meant to make the
instructions simpler? If users start to read only those they will miss
lots of details of the migration process.

On 2013-10-31 04:41, MacPorts wrote:
> +=== A simple example ===
> +run as root

This instruction alone is not simple.

I would discourage use of the root account directly. Only run those
commands that really require elevated privileges as root.

> +{{{
> +xcode-select --install
> +xcodebuild -license
> +echo "install this then press enter https://distfiles.macports.org/MacPorts/MacPorts-2.2.1-10.9-Mavericks.pkg"

The migration instruction do not target Mavericks only. Linking to a
single package installer is wrong.

> +read YNM
> +cp /opt/local/etc/macports/macports.conf ~/Downloads/macports.conf.old
> +cp /opt/local/etc/macports/macports.conf.default /opt/local/etc/macports/macports.conf
> +PL=~/Downloads/my_requested_ports.txt

Why use ~/Downloads? These files are not a downloaded.

Depending on how you got root, $HOME might refer to different
directories (/Users/julesverne vs. /var/root).

Why copy macports.conf in these instructions, but not sources.conf or
archive_sites.conf? variants.conf or pubkeys.conf should not need updates.

> +port -q installed requested | perl -pe 's/@.*//g;s/ +//g' | sort -u > $PL
> +echo "make sure you want everything listed in $PL then press enter"
> +read YNM
> +port -f uninstall installed
> +port clean all
> +port install $(cat $PL | perl -pe 's/\n/ /g')
> +}}}
> +this example will ignore variants, compile flags, you may have used originally.

Compile flags? Where would they come from?

Rainer