Handling the movement of a header file between packages

Adam Mercer ram at macports.org
Wed Dec 28 14:35:23 PST 2011

On Wed, Dec 28, 2011 at 21:36, Clemens Lang <cal at macports.org> wrote:

> you could add a pre-activate-block, check for the existance of the file,
> check whether it is owned by the old port and if it is, remove it and
> delete the registry entry for it.
> That probably only possible using MacPorts-internal interfaces for the
> registry, though. I'm not sure deleting the file without removing it
> from the registry is enough for the activation to continue successfully
> and it probably is not good idea anyway in regard to database
> consistency.

I agree, manually messing with the registry sounds like a bad idea.
Maybe the best option is to simply check for the problem file and then
fail with a message stating the way to manually resolve it.



More information about the macports-dev mailing list