Deactivating a port

Paul Guyot pguyot at
Wed Mar 21 21:19:05 PDT 2007

On Mar 22, 2007, at 1:13 PM, John Ridgway wrote:

> Friends -
> I'm creating some new ports -- stuff from CTAN for TeX, and I am  
> discovering a real need for a pre- or post- deactivate hook  
> (preferably both, but I could live with only post-).  What are the  
> chances that this functionality could get in to the base?  The  
> reason is that when adding fonts to a TeX tree one needs to run  
> updmap-sys to make the fonts available, but when they go away again  
> we need to run updmap-sys again...
> I just like to clean up after myself. :-)

This is one of the design problems we have. If you install port A  
version 1, that declares a (pre|post)-deactivate hook and then  
upgrade your dports/ tree with the new portfile for version 2 that  
does not declare the hook, then the very hook is no longer stored  
anywhere in your disk.

We should save the whole portfile in the receipt to be able to  
implement that feature.
I believe this also applies to dependencies. If port A version 1  
depends on port B and version 2 does not depend on port B, port(1)  
will let you uninstall B without telling you you are breaking port A  
(version 1).


More information about the macports-dev mailing list