Diego Elio Pettenò wrote: > > Ah, I always thought of overlays as places where apps tend to reside, > > but of course you could have glibc in there for all we know... Good > > point... > > Welcome to the life of your average Gentoo ebuild maintainer.
Stop complaining (and with foul language! come on, you sound like an idiot, which seems unneccessary) and let's think about solutions. Do I understand correctly that you consider the problem to be that it's not clear whether a system in a bug report has ebuilds from an overlay in the dependency chain or not? A very low resolution solution would be a tainted flag like the one in the kernel, but perhaps we can do something a bit better. emerge could output this information sometime before src_unpack. It would be very visible in every emerge log, and it would certainly be helpful for everyone who understands overlays - it's certainly easy to imagine that it could completely preempt some invalid bug reports. If I do an emerge I typically know if I want dependencies out of an overlay or not. Another potentially interesting vector is to add overlay policies to ebuilds, although this means introducing arbitrary limitations, which generally doesn't make sense. I'm sure there are more and better interesting solutions to this problem. Let's hear? //Peter
