Summary: | =sys-kernel/genkernel-next-55 wants 80-drivers.rules but sys-fs/eudev[-kmod,modutils] installs 80-drivers-modprobe.rules instead | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | gentoo_2014 |
Component: | Current packages | Assignee: | Fabio Erculiani (RETIRED) <lxnay> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | eudev |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
gentoo_2014
2014-05-05 13:29:44 UTC
The file has been around since 2012-04-04 up to this day at upstream udev wrt: http://cgit.freedesktop.org/systemd/systemd/log/rules/80-drivers.rules Why, and how, does eudev not install it? Is it renamed for some reason? https://github.com/gentoo/eudev/blob/master/rules/Makefile.am has: if HAVE_MODULES if HAVE_LIBKMOD dist_udevrules_DATA += \ 80-drivers.rules else dist_udevrules_DATA += \ 80-drivers-modprobe.rules endif endif So, with USE="-kmod modutils" the file gets renamed to 80-drivers-modprobe.rules, and this is sys-fs/eudev specific problem, no other implementation has file called '80-drivers-modprobe.rules' ping? maybe it's time to add !sys-fs/eudev[-kmod,modutils] blocker to genkernel-next ebuild? (In reply to Samuli Suominen from comment #3) > ping? > > maybe it's time to add !sys-fs/eudev[-kmod,modutils] blocker to > genkernel-next ebuild? That seems valid to me, if genkernel-next doesn't want to grab 80-drivers*.rules ... (In reply to Ian Stakenvicius from comment #4) > (In reply to Samuli Suominen from comment #3) > > ping? > > > > maybe it's time to add !sys-fs/eudev[-kmod,modutils] blocker to > > genkernel-next ebuild? > > > That seems valid to me, if genkernel-next doesn't want to grab > 80-drivers*.rules ... We've promoted kmod to +kmod in the USE flags for 1.8 and 9999 as a small step in this direction. You shouldn't hit the issue if you use the defaults. (In reply to Ian Stakenvicius from comment #4) > (In reply to Samuli Suominen from comment #3) > > ping? > > > > maybe it's time to add !sys-fs/eudev[-kmod,modutils] blocker to > > genkernel-next ebuild? > > > That seems valid to me, if genkernel-next doesn't want to grab > 80-drivers*.rules ... We're going to keep the current kmod/modutils structure upstream, so please just add that blocker to genkernel-next and then close this bug. I am not interested in supporting eudev in genkernel-next, but patches are always welcome. (In reply to Ian Stakenvicius from comment #4) > (In reply to Samuli Suominen from comment #3) > > ping? > > > > maybe it's time to add !sys-fs/eudev[-kmod,modutils] blocker to > > genkernel-next ebuild? > > > That seems valid to me, if genkernel-next doesn't want to grab > 80-drivers*.rules ... (In reply to Fabio Erculiani from comment #7) > I am not interested in supporting eudev in genkernel-next, but patches are > always welcome. OK then + 06 Jul 2014; Samuli Suominen <ssuominen@gentoo.org> genkernel-next-55.ebuild, + genkernel-next-58.ebuild: + Block sys-fs/eudev with USE="-kmod modutils" wrt #509624 (In reply to Samuli Suominen from comment #8) > (In reply to Ian Stakenvicius from comment #4) > > (In reply to Samuli Suominen from comment #3) > > > ping? > > > > > > maybe it's time to add !sys-fs/eudev[-kmod,modutils] blocker to > > > genkernel-next ebuild? > > > > > > That seems valid to me, if genkernel-next doesn't want to grab > > 80-drivers*.rules ... > > (In reply to Fabio Erculiani from comment #7) > > I am not interested in supporting eudev in genkernel-next, but patches are > > always welcome. > > OK then > > + 06 Jul 2014; Samuli Suominen <ssuominen@gentoo.org> > genkernel-next-55.ebuild, > + genkernel-next-58.ebuild: > + Block sys-fs/eudev with USE="-kmod modutils" wrt #509624 To be clear, its not that genkernel-next doesn't play nice with eudev. Its just that you have to have +kmod and -modutils. This should be fine, so we keep the backwards compatibility. (In reply to Anthony Basile from comment #9) > (In reply to Samuli Suominen from comment #8) > > (In reply to Ian Stakenvicius from comment #4) > > > (In reply to Samuli Suominen from comment #3) > > > > ping? > > > > > > > > maybe it's time to add !sys-fs/eudev[-kmod,modutils] blocker to > > > > genkernel-next ebuild? > > > > > > > > > That seems valid to me, if genkernel-next doesn't want to grab > > > 80-drivers*.rules ... > > > > (In reply to Fabio Erculiani from comment #7) > > > I am not interested in supporting eudev in genkernel-next, but patches are > > > always welcome. > > > > OK then > > > > + 06 Jul 2014; Samuli Suominen <ssuominen@gentoo.org> > > genkernel-next-55.ebuild, > > + genkernel-next-58.ebuild: > > + Block sys-fs/eudev with USE="-kmod modutils" wrt #509624 > > To be clear, its not that genkernel-next doesn't play nice with eudev. Its > just that you have to have +kmod and -modutils. This should be fine, so we > keep the backwards compatibility. Correction, that's +kmod,+modutils -- if USE="-modutils", then there is no module support at all in eudev, regardless of whether USE="kmod" is set or not. At any rate, the block added is correct. Thanks for fixing! |