On Fri, Nov 11, 2011 at 08:58:14AM +0100, Tom???? Chv??tal wrote: > Hi guys, > > In last 3 days i recompiled chromium 3x > > 1x rebuild for cups useflag > 1x update > 1x rebuild for cups useflag
<snip> Chromium moves fast and you're obviously running unstable keywording. Meaning you're *intentionally* getting every beta channel release. Nicely phrased, your complaint is that having ran unstable keywords, it's moving too fast for your taste. Stable keywords seem like an obvious solution to it. One thing that is less obvious is that there are essentially two flavors of unstable chromium- dev and beta. Currently beta is 17.*, dev is 16.*. If you don't want bleeding edge, but want faster than stable, pmask 17.*. That said... you're complaining that having ran unstable, you're having to rebuild too much. Stable exists for a reason. Either way, I suggest folks flip through the changelog- not seeing anything egregious in bumping, refactoring appears to go out during upstream version bumps. For the cups rebuild referenced above is a build compilation failure that was rolled out in existing versions (or in version bumps). It may be an annoyance to Tommy that emerge -N picked it up, but for folks hitting the build failure, they obviously view it a bit differently (as evidenced by a fair amount of bitching on the bug in question). If you really, really want to keep running bleeding edge, rebuilding for every change that occurs on it but selectively slowing down certain builds... well, patch portage and mangle the existing vcs rebuild code to be usable for other packages, adding a feature along the lines of "I want to run bleeding edge X, but rebuild it only weekly". Barring that, the solutions for your user configuration problem are above. ~harring
signature.asc
Description: Digital signature
