All, This bug is a tracker for things that need to be done before >=udev-182 can be stabilized. I would prefer that no comments be put on this bug, but that we have other bugs block this tracker. This way, everyone sees what needs to be done before we can stabilize newer versions of udev.
Looks like now the real blocker is bug 421839, but not sure how to proceed with it :(
(In reply to comment #1) > Looks like now the real blocker is bug 421839, but not sure how to proceed > with it :( That bug has been removed from the blockers for this tracker; it doesn't have any bearing on when we can stabilize the newer udev.
I think bug 442384 is serious enough to block this one, as sys-apps/kmod should be capable of picking up both /usr/lib/modprobe.d and /lib/modprobe.d Also changed target of stabilization to 196-r1
*** Bug 450938 has been marked as a duplicate of this bug. ***
I'm sorry, is that something wrong with me or udev-197-r3 is being stable for at least a few days?
(In reply to comment #5) > I'm sorry, is that something wrong with me or udev-197-r3 is being stable > for at least a few days? Since udev-197-r3 is now stable on amd64/x86 and installs to / just like udev-171 installed, the path to modprobe.d is back to /lib/modprobe.d So Comment #3 now moot. So yes, new udev is being stabilized in bug 452556 and once it's done, udev-171 and module-init-tools leaves the tree. It's 197-r3 or higher or sys-fs/eudev if you need kernel older than 2.6.39. Otherwise there is no need to change.
(In reply to comment #5) > I'm sorry, is that something wrong with me or udev-197-r3 is being stable > for at least a few days? And re-read Comment #0 and lets stop talking here. Use http://forums.gentoo.org/ if you have move helpdesk questions. Thanks.