#19176: patch to fixup existing uninstall implementation ----------------------------------------+----------------------------------- Reporter: david.osguthorpe@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: MacPorts Future Component: base | Version: 1.7.0 Keywords: | Port: ----------------------------------------+----------------------------------- Comment(by blb@…): Replying to [comment:3 david.osguthorpe@…]:
I added this because someone was asking for such a procedure on the mailing list recently - Im not sure what you mean by pkg_uninstall is not actually used - you mean that no Portfile defines it - it would only be defined in Portfiles - not in base itself
Right, I didn't find any Portfiles which actually define pkg_uninstall.
Well it does actually enable you to do something at uninstall - I was
just pointing out that its run in a different context to the rest of the Portfile - its actually probably not useful that destroot is defined - by uninstall time for a normal port install the whole work directory would have been deleted at the install stage in any case - Ive just never sorted out in detail what variables are defined - but theres enough information to operate explicitly on paths you know about - which is what I am using it for (since 1.3/4 odd) True, and having a pre/post-deactivate and uninstall step is definitely something which would be useful, but I'm not sure if this is the way to do it. It's correct that ${destroot} wouldn't be useful during uninstall, but what other bits may be? I think the better solution is to allow deactivate and uninstall hooks in the Portfile and they can be run by port just like with other, similar steps. I think my primary issue with it is that this method is so different than the rest of the way Portfiles work, though it does have the advantage of being implemented... -- Ticket URL: <http://trac.macports.org/ticket/19176#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS