This procedure will install a pristine MacPorts system and, if the optional steps are taken, remove the as of now unnecessary MacPorts-2.7.2 source directory and corresponding tarball.
Changelog- there's a macosforge supported repository with buildbots that produce signed archives and the default is to fetch these binary archives rather than building from source (that you can force using -s flag). rm -rf MacPorts-2.7.2 These steps need to be perfomed from an administrator account, for which sudo will ask the password upon installation. Consider as example the case of a somehow big package that takes few hours to be built and compare this to the time of downloading it as an archive having a. And as i mentioned, at this point in time its pretty damn quick to set most things up. Which is what you want of a Package Manager really.
The installation may take an hour or two to complete. Other than that though I'm a big fan of the MacPorts philosophy of building its own little world & not relying on some prepackaged OS X library - when it works, and it mostly does, everything is dead simple. That said I see the question is quite old, since 2.0 there's support for binary archives -cf. Look up sudo Unix if you dont know what the sudo command does. If you experience a huge difference when building a program outside of MP you should file a ticket on the issue tracker with the details. MacPorts uses Apple's tools to build and it only adds a negligible overhead to the same build time that you would get outside of MacPorts, the bigger the package, the smaller the difference. So, yes, accordingly with Ryan, it might take more than 2 hours depending on the machine. MacPorts used to only build from source and this can lead to a difference of several orders of magnitudo when compared to a package system that fetch binaries.Ĭonsider as example the case of a somehow big package that takes few hours to be built and compare this to the time of downloading it as an archive having a size of a few tens of MBs. I really recommend switching Time Machine off during a MacPort session, as it tries to back. Ive just done the installation (Mac OX 10.6.6 intel i7 8Gb) and it took approximately 1hr and 30 minutes to finish the build and the installation was successful. I changed up the instructions a bit since we’re not dealing with the ppc architecture any longer: sudo port -v clean irssi +perlĬd /opt/local/var/macports/build/_opt_local_var_macports_sources_release_tarballs_ports_irc_irssi/irssi/work/
Another trac ticket (from four years ago) on the MacPorts site gave some pointers on how to work around the bug for a previous version. I opened a ticket in trac and began looking for a workaround. Sure enough, when I looked at the lines in the output, both x86_64 and i386 were passed to the compiler. During the build, I saw quite a few errors from the compiler: -E, -S, -save-temps and -M options are not allowed with multiple -arch flags However, I was sad to see that irssi wouldn’t build via MacPorts on OS X Lion. Exclude dependencies only required at build time, i.e., fetch, extract. I’ve floated back and forth between graphical IRC clients and terminal-based clients for a long time. Updating the ports tree -> MacPorts base is outdated, installing new version.