On Mon, Feb 26, 2018 at 11:16 AM, Nikos Chantziaras <rea...@gmail.com> wrote: > On 26/02/18 17:59, Rich Freeman wrote: >>> >>> Can't you whitelist packages like automake so that they don't trigger >>> rebuilds? Or at least provide a configurable whitelist (for make.conf) >>> where >>> we can add packages that don't trigger changed-deps rebuilds? >>> >>> There is no reason to rebuild anything just because of an automake >>> update. >>> This is just madness. >>> >> >> Are you using --deep? I suspect that is why changed-deps is looking >> at build-time dependencies. I don't see why you'd need to rebuild >> something if a build-time dependency changes, unless you really care >> about building with the latest build system (in which case you >> probably would want to rebuild after an automake update). > > Yes, I use --deep. I've run into cases many times in the past where portage > was skipping updates unless I used --deep. >
You might want to avoid combining both --deep and --changed-deps. I haven't tested this but I suspect it is why you're getting all the automake-related rebuilds. Granted, at present that would require two separate updates if you wanted to use both. It seems like a whitelist isn't really the right solution here. I could see having a way to tell --changed-deps to ignore build-time dependencies as useful. Of course, the real solution is revbumps whenever necessary, but getting devs to do that seems to be impossible, as everybody wants to assume that dynamic deps work. -- Rich
