On Mon, 2005-01-17 at 19:31 +0100, Thomas de Grenier de Latour wrote: > 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.
You are quite alright. This feature was extremely new. I'm glad it comes
to some immediate use to you.
> 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).
This is still facing some interesting design issues. I think the general
idea will be to support split firmware/util&driver packages, and then
look at implementing a solution to address the "I dont want the
userland" stuff.
There is already a semi-working suggestion to store module source, and
build metadata in a file which can be automatically rebuilt when a new
kernel is installed using a separate tool.
This is easy to accomplish with linux-mod.
There is also perhaps the idea of introducing (please dont yell at me
all you anti-symlink lovers) a "module-userland" use flag, which will
prevent the build of the userland tools.
Perhaps this can be done with a seperate function which can be defined
in the module ebuild.
something like:
src_compile_userland() {
does userland compiles, prior to building the modules.
is is only run if USE="module-userland" is set.
}
and then enable this USE flag by default.
I will actually copy this to kernel@ to get comments on the above since
I'm all of a sudden struck liking the idea :)
Tied in with the other thread of mine, it could be easily automated on
kernel upgrade. ie:
if just upgraded kernel
then
USE="-module-userland symlink" emerge ${modules installed based on file
content}
fi
type logic.
--
Role: Gentoo Linux Kernel Lead
Gentoo Linux: http://www.gentoo.org
Public Key: gpg --recv-keys 9C745515
Key fingerprint: A0AF F3C8 D699 A05A EC5C 24F7 95AA 241D 9C74 5515
Web:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x9C745515
signature.asc
Description: This is a digitally signed message part
