Well, since the hotplug now looks in /lib/firmware, shouldn't the ebuilds now "dodir /lib/hotpug" instead of "dodir /usr/lib/hotplug/firmware" in src_install?
Oop, I meant "dodir /lib/hotplug"
Created attachment 80931 [details]
Edited ebuild 20030805-r2
Created attachment 80932 [details]
Passed through sed....
Created attachment 80933 [details]
Created attachment 80934 [details]
more sed output....
Created attachment 80935 [details]
again with the sed...
Created attachment 80936 [details]
you get the point...
Created attachment 80937 [details]
Created attachment 80938 [details]
This about drove me crazy until at last I figured it out. Since there are tons of HOWTOs telling you to
do things to /usr/lib/hotplug/firmware, it might be a good idea for the ebuild to
make a sym link for a while.
I'd second Chris Xe's suggestion. I found my server didn't load some firmware on boot, checked /etc/hotplug/firmware.agent (which seemed to still say /usr/lib/hotplug/firmware), and tried /lib/hotplug on an off chance, and it worked, so headed over here to look for bug reports.
It was /etc/hotplug/firmware.agent that threw me... mine reads:
# directory of the firmware files
which kind of throws you if you're diagnosing.
All our ebuilds install firmware into /lib/firmware; the directory installed by hotplug is thus completely useless (moreover gets unmerged completely on re-emerging hotplug, as there's no keepdir in the ebuild).
As an added bonus, having hotplug installed actually kills firmware loading w/ >=udev-096 - see Bug 147006. I kinda miss the reason why we still have hotplug, causes more harm than good.
sys-apps/hotplug is useless with any recent udev version, and 2.4 kernels are no longer supported. Unmerge it and move on.