-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 15/01/13 02:20 AM, Michael Weber wrote: > Hi folks, > > this commit changes the set of USE flags on the just stabled > gcc-4.6, running a huge number into an rebuild of an freshly > updated package. (emerge --newuse recaclulates from "go disabled" > to "go missing") > > Wouldn't it be possible to a) refrain from this change (really, who > has USE=go turned on?) b) handle this with package.use.mask, c) > figure it out before stabilization > > I see the point in nobody beeing perfect, but these recurring > effect-less rebuilds of widespread base packages set me up. > > Imho, editing /var/db/pkg/sys-devel/gcc-4.6.3/USE is not a recipe > to be carried out to the user. But can we do stuff like this in > profile updates? Without hurting system with USE=go activated, > which need actually need the recompile. > > my 2 cents > > Michael >
" emerge -uD --reinstall=changed-use @world " This skips rebuilds for packages that receive new use flags or have use flags removed but were already disabled. Unfortunately it's not as convenient to type as -uDN , but it does keep your system updated while skipping spurious/unnecessary rebuilds. [tangent] I wonder if it might be pertinent for future portage's to install an alias command, "emerge-system-update" or similar, that would wrap the standardly accepted emerge update command more or less everyone already runs.. easier end-user experience as they don't need to learn/remember all the little fiddly options, plus portage dev's can control the default (probably we make it over-ridable via a make.conf var or something) so that if things change with newer EAPIs or portage features the default flags can be adjusted too... [/tangent] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlD1XUwACgkQ2ugaI38ACPA0WQD/RPIat2/eR6x2qRblQsc5xyVs IhOj7bQdrM5Uou/Zn1cBAKnsBMYRlw4ZVhqOT7/4XCOl824dFp543jAO+hJeuErm =zVJr -----END PGP SIGNATURE-----
