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