I am making an ebuild for module-init-tools. This is the new version of modutils for the development kernel, if you have 2.5.47 or greater, you need this to make modules work. When the makefile installs, it moves the old mod utils to *.old (examp /sbin/insmod -> /sbin/insmod.old). The reason it does this is that so when you use an older kernel, it will use the older modutils... I am not sure how to handle this with portage. Any thoughts on how I could make this work?
Created attachment 5988 [details] module-init-tools 0.7 ebuild
Created attachment 6093 [details] module-init-tools-0.8.ebuild This is a fully working ebuild... The only problem is that it overwrites the modutils files. It does manage to retain backawards compatability with them though. Would be nice to change the development-kernel to depend on this.
Created attachment 6128 [details] module-init-tools-0.8-r1.ebuild New ebuild, added the translation of modules.conf -> modprobe.conf (modules.conf is unchanged) and added dependency on development-kernel >= 2.5.47
Created attachment 6129 [details] module-init-tools-0.9.ebuild beta ebuild updated for 0.9-beta. docs for moudule-init-tools fixed.
Created attachment 6229 [details] module-init-tools-0.9.1.ebuild Updates to new version, fixes needed for 2.5.48+ not 2.5.47. Renaming the old modutils made much slicker, thanks to an change from rusty for me ;)
ok, I'm poking at it, didn't work quite right the way it was, but I'll have it under control momentarily. Just ripping out the rename code from the makefile since the makefile has /sbin specified literally not variably
in portage, check it out, enjoy, and e-mail me if I forked it in any way.
Closing old bugs.
