On Sun, 16 Jan 2005 22:56:08 +0000 John Mylchreest <[EMAIL PROTECTED]> wrote:
> > One thing I will suggest is looking at my recent linux-mod > > commits wrt CONFIG_CHECK="@OPTION:module" syntax. this will > > exclude the module if the OPTION exists in the kernel config, > > and will still build userland tools. > > I have committed an update to fuse-2.2_pre3 to demonstrate how > this should be used. please let me know your thoughts on this. Well, thanks for your answer and for giving an example with Fuse. I think this is an elegant solution to the "my kernel already have this module" issue, which was the top item on my list. I've applied the same trick to the shfs ebuild to test it a bit (bug #78387), and that's really very convenient. Actually, i would probably not have posted my message if i had new about the features of this eclass, sorry about that. The remaining issues are rather minor, it's just about having to recompile from time to time things that don't need it when installing new instances of a module (but that's no big deal), or installing a module that will never be used (the slmodem case - for that one i will write a splitted ebuild, and see what maintainers think). Thanks, -- TGL. -- [email protected] mailing list
