Deactivating a port

[Daniel J. Luke]

On Mar 22, 2007, at 12:19 AM, Paul Guyot wrote:
> 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.

We do save it if archive mode is on... (although as far as I know,  
nothing makes use of that).

> 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).

oh, ick ... I thought that that was tracked somewhere else.
--
Daniel J. Luke
+========================================================+
| *---------------- dluke at geeklair.net ----------------* |
| *-------------- http://www.geeklair.net -------------* |
+========================================================+
|   Opinions expressed are mine and do not necessarily   |
|          reflect the opinions of my employer.          |
+========================================================+


-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.macosforge.org/pipermail/macports-dev/attachments/20070322/a1e32d3f/PGP.bin