Summary: | emerge -pvuND world, rebuilds package even there is only one new useflag | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Bernd Bednarz <bbednarz> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | wschlich |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Bernd Bednarz
2007-03-11 17:04:19 UTC
that is expected behavior when using the -N flag. There are many reasons for it even if you never had said flag enabled. I understand why the packages has been rebuild on Bug #156527 But for this case there comes a new useflag and the portage know if I want to build it or not. So thatswhy emerge want to rebuild my gcc? if I uses "-d" flag the gcc will be rebuilded too NOT a bug, completely irrelevant whether there's one or zillion of new flags. I couldn't understand why I have to rebuild a package even if I changed something. I think it is waste of cpu. (In reply to comment #4) > I couldn't understand why I have to rebuild a package even if I changed > something. You don't "have to". The option is called --newuse, not --select-things-I-must-rebuild-ASAP (In reply to comment #4) > I couldn't understand why I have to rebuild a package even if I changed > something. > I think it is waste of cpu. Here's a little hack that will prevent that flag from triggering --newuse: mkdir -p /etc/portage/profile echo d >> /etc/portage/profile/use.mask |