| 1 |
El dom, 19-01-2014 a las 11:23 +0100, Alexander Berntsen escribió: |
| 2 |
> On 19/01/14 09:01, Pacho Ramos wrote: |
| 3 |
> > If I understand the change correctly (I don't know much about |
| 4 |
> > python but, but per the diff, looks like you are dropping the |
| 5 |
> > option and making the code behave like it's always 'True'), seems |
| 6 |
> > that you are forcing autounmask to be on always. |
| 7 |
> You do not understand it correctly. It makes --ask imply |
| 8 |
> --autounmask-write. |
| 9 |
|
| 10 |
Ah, nice :) |
| 11 |
|
| 12 |
> |
| 13 |
> > Even if I use this in all my systems (passing it in by default |
| 14 |
> > emerge opts), I think we still need a way to disable it sometimes. |
| 15 |
> There is. Regardless of whether you mean (current) --autounmask or |
| 16 |
> (current) --autounmask-write behaviour. |
| 17 |
> |
| 18 |
> emerge --ask foo # This won't -write |
| 19 |
> emerge --autounmask --pretend foo # Same as the above |
| 20 |
> emerge --ask --pretend foo # This won't even offer the suggestions |
| 21 |
> |
| 22 |
> Please see [0] for more information. |
| 23 |
> |
| 24 |
> [0] <https://bugs.gentoo.org/show_bug.cgi?id=481578#c10> |
| 25 |
|
| 26 |
Then, I guess "-ap" would be the equivalent of --autounmask=n and should |
| 27 |
behave in the same way, right? In that case, no problem (even if I think |
| 28 |
we should document this since using --ask --pretend at the same time |
| 29 |
doesn't look so intuitive to me :( ) |
Archives