For the unloading issue, I believe that we should require any package which
has a kext to do the following:
1) in a pre-remove script, have a dialog with the user in which the user
is told that an immediate reboot will occur if this package is removed,
and if the user says "no", the removal operation is cancelled
2) in a post-remove script, (gently) force a reboot.
As far as where to put it: does Apple have a recommended place (default
search path?) to install third-party kexts? /Library/Extensions, maybe?
If so, along the lines of earlier discussions, we should consider expanding
our rules to allow /sw/Library/Extensions as the location for kexts.
We really need to reach a consensus, and soon, about these proposed
extenstions to the FHS. (I'm referring to /sw/Library/foo and
/sw/Frameworks.)
-- Dave
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
