1 |
On Sun, 19 Jan 2014 11:47:34 +0100 |
2 |
Alexander Berntsen <alexander@××××××.net> wrote: |
3 |
|
4 |
> -----BEGIN PGP SIGNED MESSAGE----- |
5 |
> Hash: SHA256 |
6 |
> |
7 |
> On 19/01/14 11:32, Pacho Ramos wrote: |
8 |
> > Then, I guess "-ap" would be the equivalent of --autounmask=n and |
9 |
> > should behave in the same way, right? In that case, no problem |
10 |
> > (even if I think we should document this since using --ask |
11 |
> > --pretend at the same time doesn't look so intuitive to me :( ) |
12 |
> Since --ask implies --autounmask, the following are all the same for |
13 |
> autounmask-purposes: |
14 |
> |
15 |
> emerge --pretend --ask foo |
16 |
> emerge --pretend --autounmask foo |
17 |
> |
18 |
> As for "emerge --autounmask=n foo", This will actually spit out the |
19 |
> suggestions, just not ask to write them. |
20 |
> |
21 |
> While playing with this, I discovered a possible misbehaviour though. |
22 |
> With "emerge --ask --autounmask=n", --ask takes precedence to |
23 |
> - --autounmask=n. Maybe it shouldn't. But this can always be changed. |
24 |
> - -- |
25 |
> Alexander |
26 |
|
27 |
As I recall in portage's code, -p -s ignored and removed from the |
28 |
options when --ask is invoked since it implies --pretend behavior, but |
29 |
allows emerge to continue with an yes answer rather than have to start |
30 |
the dep calc's over again. |
31 |
|
32 |
So, I agree that having to have both --ask and --pretend to get the |
33 |
same functionality is just bad and not intuitive. |
34 |
|
35 |
Brian Dolbec, <dolsen> |