On Tue, 12 Feb 2013 20:51:15 +0000 (UTC) Duncan <1i5t5.dun...@cox.net> wrote:
> Christopher Head posted on Tue, 12 Feb 2013 11:38:14 -0800 as > excerpted: > > > On Sun, 10 Feb 2013 20:43:02 +0100 Dirkjan Ochtman <d...@gentoo.org> > > wrote: > > > >> On Sun, Feb 10, 2013 at 5:54 PM, Fabio Erculiani <lx...@gentoo.org> > >> wrote: > >> >> +1 from me; I've had a few machines break on kernel upgrades > >> >> because I didn't have the proper firmware installed (I guess > >> >> older kernel sources came with the firmware?). > > >> > For starters, if kernel sources provide /lib/firmware, how do you > >> > deal with file collisions? > > > > Please don't make kernel sources RDEPEND on firmware. The kernel > > DOES NOT depend on firmware to work properly. Well over half my > > machines prove that: they work perfectly fine (read: 100% of their > > hardware works) with no firmware at all installed. > > Not a problem as long as the RDEPEND is under USE=firmware or similar. > No USE=firmware, no rdepend! =:^) > > Kernel sources providing /lib/firmware itself shouldn't be a problem > either, as that's just a dir, which many packages may own. The > individual firmware files would be a problem, but the USE=firmware > RDEPEND solution should solve that. > Yes, of course, I meant please don’t depend unconditionally. A conditional depend is fine by me, and I don’t care about one random directory being created—I just don’t want a whole package being pulled in for nothing. Chris
