BUG: problem deactivating adium port

[reilles@…]

the adium port leaves files behind it when it is deactivated.

I deactivated the 0.62 version of adium port, in order to install the new one.

The build and install phases are fine, but i get ---> Activating adium 0.63_0 Error: Target com.apple.activate returned: Image error: /Applications/DarwinPorts/Adium.app/ Contents/PlugIns/Gaim.AdiumPlugin/Contents/Frameworks/Libgaim.framework/Libgaim already exists and does not belong to a registered port. Unable to activate port adium.

Indeed, these files are left by the deactivate target. Workaround is to manually remove the /Applications/Darwinports/Adium.app directory (activate -f should work too) This problem happens only with different versions of the adium port. port deactivate adiium && port activate adium works

[olegb@…]

assigning to maintainer

[rshaw@…]

There are two problems at work here.

[rshaw@…]

This actually looks like a combination of two problems:

One is a bug in the base/ code where the uninstall code is not properly removing symbolic links that point to non-existant files. I will look at this and fix it.

The second is the port itself since the installed port is apparently creating symbolic links to things using an absolute path:

`-- PlugIns

`-- Gaim.AdiumPlugin

`-- Contents

`-- Frameworks

`-- Libgaim.framework

Headers -> /opt/darwinports/dports/aqua/adium/work/adium/Plugins/Gaim Service/Libgaim.framework/Versions/Current/Headers

This would of course not run once you clean your port build area since the files are pointing off to the build space instead of the Adium.app location. Toby will need to fix this one.

-rshaw

[rshaw@…]

Ok, the problem with symlinks not being removed during deactivate has been fixed in the base/ code.

-rshaw

[rshaw@…]

The Adium port should now properly deactivate with the latest base/ code fixes. However, existing installations will not deactivate properly since the problem came from the contents file map being incorrect (missing symlinks). Once you reinstall using the new base/ code, the deactivate should work correctly.

-rshaw