On Sat, 26 Jul 2014 16:05:58 +0000 (UTC) Martin Vaeth <mar...@mvath.de> wrote: > Ciaran McCreesh <ciaran.mccre...@googlemail.com> wrote: > > Your solution fails spectacularly in the following ways: > > > > * Ebuild removal > > Already discussed as to fail with static deps, too.
Uh, static dependencies don't behave any differently when an ebuild is removed. I don't think you understand how that works. > > * Overlays > > Not an issue: Exactly the information of that ebuild > which *would* be used if you reemerge contains > the relevant data. The association between an installed package and "the ebuild it came from" doesn't work correctly when overlays around. Again, you don't understand the issue. > > * Introduction of :=3D dependencies > > This is not a "minor update" in dependencies > and thus requires a revbump. So what is a "minor update", and what are you planning to do to prevent what you call "useless rebuilds" when := dependencies are introduced? > > * pkg_*rm > > Not related. Yes it is. Read and understand the previous discussion about the ruby-config issue. -- Ciaran McCreesh
signature.asc
Description: PGP signature
