There's another option for you that might save you diskspace in return for time. I've noticed that MacPorts ports tend to depend on the full set of dependencies a given project could have, ffmpeg being a good example. They also tend to install things you probably already have installed, like X11 and python. So depending on what apps you require to have available at all times, you could install the minimal dependencies for your application through MacPorts, and then build the app yourself. I suppose this would also allow more control/selectivity over what ports get built as universal in case you want to install a 32bit app. (My ports tree explosed when I needed a 32bit version of ffmpeg...)
R On 17 Aug 2013, at 02:45, Bob M <[email protected]> wrote: > Thank you Sterling, Ryan, Lawrence, Chris - I have followed your > suggestions, moving the whole of the macports build tree and changing > portdbpath as suggested by Lawrence, then cleaning up inactive > installs as suggested by Chris and Ryan (I hit minor problems with > py2x-distribute in a few cases, had to 'port -u uninstall' it because > of spurious dependencies - I'm mentioning this so it's google-able). I > have successfully done a 'port upgrade outdated', I've been able to > move back some directories to the mac that I had previously had to > remove - and still have 11GB free! > > I deeply thank you for your helpfulness, it's really appreciated. Now > does anyone know about booting fedora from an lvm install on a > software RAID array 8^). > > Best Wishes > Bob > _______________________________________________ > macports-users mailing list > [email protected] > https://lists.macosforge.org/mailman/listinfo/macports-users _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
