Hi Rob, You brought up the subject of adding a kext to fink on #fink today. I belive I said "Nooooo!" or some such :)
Well, lets actually discuss it, I have changed my opinion a little. If you want to package something that requires a kext then the kext would:
1) go in a new category, "naughty" or something to clearly identify it as not going in /sw.
2) would not install (preinstscript) without the user typing a phrase. No defaults, make sure fink --yes will not install it without user interaction.
3) would not install anything in /System/Library/Extensions, but would install somewhere in /sw and in a postinstscript add a symlink. This way a user who does sudo rm -rf /sw would be left with a dangling symlink in /System/Library/Extensions, but would not otherwise "damage" a users system.
Add 4) to 10) of more things to make sure the user knows that the package is putting in a kext and telling them why and how to remove it and you have my agreement to add a kext to fink. Now the only problem is these others on the list =)
This kext you want to add would allow a few vpn clients to go into fink, this is a good thing, and saying "no" for the simplistic reason that apple does not look for kexts outside of /System/Library/Extensions is silly.
I would imagine that there would be other "naughty" ports too. For example I'd kind of like to package something that would have to go in Library/Image\ Capture/ for mac os x to "see" it. So there would be more than one lonely package in the new category :)
Peter -- Peter O'Gorman - http://www.pogma.com
------------------------------------------------------- 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
