[MacPorts] #31280: fuse4x-kext: move kext unload to pre-deactivate phase
MacPorts
noreply at macports.org
Tue Sep 27 19:29:14 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 anatol.pomozov@…):
> We don't, in general, shut down running software when uninstalling a
port.
fuse4x kext cannot be unloaded while it is in use. User have to stop
filesystems first.
> Really, I'm not sure we want to unload the kext when uninstalling the
port.
If we uninstall fuse4x-kext then we have to uninstall fuse4x library as
well (fuse4x depends on kext). What is the reason to run unused kext if we
cannot use it?
I found that this is an issue when I was switching fuse4x from macports
<-> fuse4x from sources. So when I do "port uninstall fuse4x" then build
and install fuse4x from sources and then run software that uses fuse4x,
the library says "version mismatch" as running (and unused) kext from
macports has version 0.8.12 but kext version in git repository is
0.8.13-HEAD. So I have to unload fuse4x-kext manually. If macports on
uninstall does the real uninstall (with kext unloading) this fixes the
problem for me.
> because the old version didn't have the post-deactivate hook and the new
version didn't have the pre-activate hook
You can insert this check twice for the transition period and later remove
the one from pre-activate.
--
Ticket URL: <https://trac.macports.org/ticket/31280#comment:3>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list