[MacPorts] #20626: patch to allow for proper functioning of pre-/post- install/uninstall/activate/deactivate procs

David Osguthorpe david.osguthorpe at gmail.com
Mon Aug 10 07:50:58 PDT 2009


> 
> Comment:
> 
>  I'd rather make these into real targets than replicate all this
>  infrastructure. Also, it might be better to wait until after the images-
>  and-archives branch is merged.
> 

I dont think this is possible - what would deactivate/uninstall depend on?
they cannot depend on install or activate (think what would happen if you then
said uninstall a target that was not installed - it would install the target
just to uninstall it - so you would always need a special check to detect that the target
was already activated/installed first)

do you like the internal munging of port install to port activate?

also if port activate is the final phase the instructions for macports should read:

to install a port with macports use the command port activate

they also cannot be the same as install targets as deactivate/uninstall are not
performed in the same environment - there is no work path, no destroot etc.
(this is also true of activate - if you do install->deactivate->activate that last
activate no longer has the work path/destroot etc. environment - probably why currently
on that last activate no pre-/post- procs are run)
in addition you would have to get the whole target system to somehow read the old
version of the Portfile (do you know how to do this? - I thought about this but
it looked as though it would require far more modifications than this working
implementation)

when will the image/archive branch be merged?

David


More information about the macports-dev mailing list