Gramps version 3.2.0 for Mac OS X

[Ryan Schmidt]

On Mar 29, 2010, at 05:17, Tim Lyons wrote:

> On 29 Mar 2010, at 06:17, Ryan Schmidt wrote:
> 
>> On Mar 28, 2010, at 12:10, Tim Lyons wrote:
>> 
>>> (1) If you had a previous installation of Gramps, you have to rename/move aside /Applications/MacPorts when you do a fresh install.
>> 
>> Why was this necessary? At most, you should have to "sudo port deactivate gramps" to move the old one aside, then "sudo port install gramps" to install the new one; I would never expect the user to need to manually fiddle with anything in /Applications/MacPorts. Ideally, deactivating the old version would not be necessary either, but I did not test upgrading.
>> 
> 
> "Fresh install" is probably not a precise enough description of what I meant.
> 
> I deleted /opt to ensure that I had a really fresh start, then installed a fresh copy of MacPorts. When Macports ran, it found the /Applications/MacPorts directory and reported that this was unexpected because it had no record of it, and then failed with the message:
> Error: Target org.macports.activate returned: Image error: /Applications/MacPorts/Python 2.6/Build Applet.app/Contents/Info.plist already exists and does not belong to a registered port.  Unable to activate port python26.

Ah yes. So the lesson here is that deleting /opt is not sufficient for uninstalling MacPorts. Correct instructions for doing so are located in the Guide:

http://guide.macports.org/chunked/installing.macports.uninstalling.html


> Anyway, I thought starting from a fresh copy of MacPorts would be a good idea because (1) I probably had lots of components that were no longer needed by Gramps, and I didn't want to keep upgrading them forever.

You could use the port_cutleaves tool to help you identify and uninstall unneeded ports. There are some previous posts on macports-users you can look up where I explain this tool in more detail.

> (2) Wouldn't starting from a fresh be the only way to really check that the dependencies were correct.

That's true, that is a way to ensure dependencies are more or less correct. Note that you could also install a second MacPorts in a different location to do this test, if you didn't want to obliterate your existing install.