sys-fs/mdadm-3.2.3-r1, and probably all other versions, have fixed path for udev rules. There is a patch attached which can solve the problem, but I doubt upstream can use such an approach, as it probably breaks cross-compiling. Reproducible: Always
Created attachment 320984 [details, diff] Get rules path from pkgconfig
I've applied a bit modified patch to Portage and then cross-compile in the ebuild by tc-getPKG_CONFIG, like this: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sys-fs/mdadm/files/mdadm-3.2.x-udevdir.patch?rev=1.1&content-type=text/plain http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sys-fs/mdadm/mdadm-3.2.3-r2.ebuild?rev=1.1&content-type=text/plain http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sys-fs/mdadm/mdadm-3.2.5-r1.ebuild?rev=1.1&content-type=text/plain
Does anyone know where mdadm bugs/patches should be sent? The upstream site only has links to webgit and that's pretty much it
I believe, linux-raid at vger.kernel.org is the right place
I've reverted the patch because the ifndef logic doesn't work. Move 'udev.pc' away and files end up in root filesystem /rules.d/ Fixed by sed in ebuild now
Comment on attachment 320984 [details, diff] Get rules path from pkgconfig If udev.pc is not available or is missing udevdir= the UDEVDIR gets set to empty value and files end up in /rules.d/ instead of /lib/udev/rules.d/ or /usr/lib/udev/rules.d/
My bad. Need to use simple expansion...
Created attachment 321134 [details] use udevlibdir for udev rule
Created attachment 321136 [details, diff] use udevdir from pkgconfig for rules.d path
(In reply to comment #9) > Created attachment 321136 [details, diff] [details, diff] > use udevdir from pkgconfig for rules.d path This works. I've imported it with a minor change to let PKG_CONFIG settable too. Only to 3.2.5-r1.
