On Fri, 20 Jan 2012 04:08:57 -0600, Dale wrote: > >> Sometimes my problem is it is like shooting skeet, it's a moving > >> target. Sometimes it moves pretty darn fast too. Zac adds it > >> faster than I can keep up. I wish they would announce new stuff > >> when it get released, both unstable and stable. Then again, > >> maybe it moves so fast he can't keep up either. lol > > > > --changed-use has been around for many years.
> It sounds like the way it works has changed tho. I don't think I have > used that option before so I don't know how it used to work. I think > the OP thinks the same. Something changed I guess. We all know > that after the build output disappeared a while back. It hasn't changed and generally works as expected. I suspect this is specific to the KDE ebuilds (or eclass). changed-use should only skip an ebuild with changed flags if re-emerging would produce exactly the same code as before, this may not be the case. For example, in some ebuilds, it is the absence of a USE flag that triggers an extra configure option, so removing that use flag would give the same code as if the package had been emerged with it enabled. Something like this happened recently with the nls flag on glibc. -- Neil Bothwick Idaho - It's not the end of the world, but you can see it from there.
signature.asc
Description: PGP signature
