Putting my Mac to sleep wedged my Installer package scripts

[Joshua Root]

You actually don't need to be connected to the internet to install the
pkg. If you're not, the selfupdate just fails and the postflight script
moves on. If rsync were to fail when the connection drops, the same
thing would happen, but when it just hangs that's harder to deal with.
This is <https://trac.macports.org/ticket/18315>.

- Josh

On 2013-5-22 17:47 , Michael Crawford wrote:
> I ran the MacPorts installer again, this time without allowing my Mac to
> sleep.  The install completed just fine.
> 
> However, I found this in my install.log:
> 
>     ./postinstall: Synchronizing local ports tree from
> rsync://rsync.macports.org/release/tarballs/ports.tar
> <http://rsync.macports.org/release/tarballs/ports.tar>
> 
> I expect that my previous install attempt failed because I put my Mac to
> sleep so I could catch a bus, then woke it up in a different place. 
> That second place had WiFi, but perhaps rsync can't tolerate its net
> connection dropping.
> 
> I think it's a really, really bad idea to hit the network from the
> installer.  I do understand why you want an up-to-date ports.tar.  If
> you're going to do this, you should warn the user that they need to run
> the installer on a network-connected Mac, as well as not allow that Mac
> to sleep during the install.
> 
> I've been using MacPorts for eons, it's a great piece of work.  I'd like
> to contribute code somehow, but as a consultant I'm just about always up
> to my ass in alligators.
> 
> Keep Up The Good Work,
> 
> Mike Crawford