[MacPorts] #31280: fuse4x-kext: move kext unload to pre-deactivate phase
MacPorts
noreply at macports.org
Mon Sep 26 03:01:19 PDT 2011
#31280: fuse4x-kext: move kext unload to pre-deactivate phase
--------------------------------------+-------------------------------------
Reporter: anatol.pomozov@… | Owner: dports@…
Type: enhancement | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Keywords: haspatch | Port: fuse4x-kext
--------------------------------------+-------------------------------------
Comment(by dports@…):
I'm not convinced this is a good idea. If anything, we'd have to do the
check in *both* the pre-activate and post-deactivate phases. If we did it
only in post-deactivate, the check would never get run on the first update
after this change (because the old version didn't have the post-deactivate
hook and the new version didn't have the pre-activate hook). Or it might
not be possible to unload the kext (because there are running file
systems) in post-deactivate, but succeed when activating the new port.
Really, I'm not sure we want to unload the kext when uninstalling the
port. We don't, in general, shut down running software when uninstalling a
port. Any reason it's especially important to do so here?
--
Ticket URL: <https://trac.macports.org/ticket/31280#comment:2>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list