after emerge --sync emerge -pvuND world ... [ebuild R ] sys-devel/gcc-3.4.6-r2 USE="fortran nls (-altivec) -bootstrap -boundschecking -build -d% -doc -gcj -gtk (-hardened) -ip28 -ip32r10k (-multilib) -multislot (-n32) (-n64) -nocxx -nopie -nossp -objc -test -vanilla" 27,699 kB ... emerge wants to rebuild my gcc even there is only a new useflag "d" wich I don't use. there is no need to recompile. Reproducible: Always I add "d" into IUSE from my gcc package and it is ok for me.
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
