John Mylchreest wrote:
> 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.
This seems like the best method in the long run, it's a lot easier for
a user to run some "build-external-modules" program than try to remember
what ebuilds to run and what useflags may need to be set. This also has
the pretty simple result that if their kernel provides the module then they
just exclude that source tree from being built.
Perhaps if possible it would still make sense to keep the module related
code in a seperate ebuild from the userspace to keep things organized
for the user, but that would be a flexable rule and only really important
for large source trees (like alsa).
>
> 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.
This method feels weird to me. If installing modules is going to be done
with ebuilds I'd prefer to just have them split into two user/kernel
packages. If it is possible to split the userland into it's own function
then it should be a pretty basic next step to just give it an 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.
>
Perhaps if automated like above then the USE flag metod would work well, but if
it is not automated it probably won't get used a whole lot as people simply
won't
remember to add "USE=-module-userland" before their emerge.Which ever way is chosen as the preferred method, if it is automated then the method won't matter to much. So I guess the important question is, which method is easier to implement, automate, and maintain? -- Michael Marineau [EMAIL PROTECTED] Gentoo Linux Developer Oregon State University
signature.asc
Description: OpenPGP digital signature
