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. :-) Peace - John
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). Paul
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@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
participants (3)
-
Daniel J. Luke
-
John Ridgway
-
Paul Guyot