1 |
Alexander Berntsen posted on Thu, 21 Nov 2013 15:23:50 +0100 as excerpted: |
2 |
|
3 |
>> 4) You're saying emerge --ask foo would write the config |
4 |
> No. Please read comment 10[0]. |
5 |
|
6 |
Quoting one example from comment 10: |
7 |
|
8 |
emerge --ask foo |
9 |
would also do what is currently done by: emerge --ask --autounmask-write |
10 |
foo |
11 |
|
12 |
Which is exactly what I said, and what you're now saying it won't do, |
13 |
while pointing at comment 10 which says exactly the opposite. |
14 |
|
15 |
It's that change in behavior based on comment 10 that I'm most |
16 |
protesting, since I depend on being able to tell portage to go ahead with |
17 |
the merges if they look good (thus the --ask), but under *NO* |
18 |
circumstances do I want it writing its changes to the various use/mask |
19 |
files. |
20 |
|
21 |
>> 5) There needs to be a way to get portage's current emerge --ask |
22 |
>> --autounmask foo (without --autounmask-write) |
23 |
> There is. This doesn't change in my patches. Please read the code or |
24 |
> comment 10[0]. |
25 |
> |
26 |
>> I'd tend to agree, but in that case, why are you wanting to do away |
27 |
>> with the ability to have portage spit out its opinion, without |
28 |
>> having portage actually do the write, while using --ask? |
29 |
> Because it can be done without --ask. See comment 10[0]. |
30 |
|
31 |
The only way you propose to do that in comment 10 is with --pretend, |
32 |
which would be a seriously negative change in behavior for my use-case, |
33 |
since it would require having portage recalculate the dependencies it's |
34 |
just calculated with the --pretend, without it. --ask currently avoids |
35 |
that situation, since when I'm happy with the output, I can simply let it |
36 |
go ahead. |
37 |
|
38 |
|
39 |
> [0] <https://bugs.gentoo.org/show_bug.cgi?id=481578#c10> |
40 |
|
41 |
|
42 |
|
43 |
-- |
44 |
Duncan - List replies preferred. No HTML msgs. |
45 |
"Every nonfree program has a lord, a master -- |
46 |
and if you use the program, he is your master." Richard Stallman |