| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 19/01/14 09:01, Pacho Ramos wrote: |
| 5 |
> If I understand the change correctly (I don't know much about |
| 6 |
> python but, but per the diff, looks like you are dropping the |
| 7 |
> option and making the code behave like it's always 'True'), seems |
| 8 |
> that you are forcing autounmask to be on always. |
| 9 |
You do not understand it correctly. It makes --ask imply |
| 10 |
- --autounmask-write. |
| 11 |
|
| 12 |
> Even if I use this in all my systems (passing it in by default |
| 13 |
> emerge opts), I think we still need a way to disable it sometimes. |
| 14 |
There is. Regardless of whether you mean (current) --autounmask or |
| 15 |
(current) --autounmask-write behaviour. |
| 16 |
|
| 17 |
emerge --ask foo # This won't -write |
| 18 |
emerge --autounmask --pretend foo # Same as the above |
| 19 |
emerge --ask --pretend foo # This won't even offer the suggestions |
| 20 |
|
| 21 |
Please see [0] for more information. |
| 22 |
|
| 23 |
[0] <https://bugs.gentoo.org/show_bug.cgi?id=481578#c10> |
| 24 |
- -- |
| 25 |
Alexander |
| 26 |
alexander@××××××.net |
| 27 |
http://plaimi.net/~alexander |
| 28 |
-----BEGIN PGP SIGNATURE----- |
| 29 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 30 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 31 |
|
| 32 |
iF4EAREIAAYFAlLbp50ACgkQRtClrXBQc7UOqgEAkTdpMbn4b0ndvME8QT1+rdVa |
| 33 |
VkYYLucfV8C3MG6DIJwBALW3zZlQeG/a/dHNdo+KuEnp/xnsUDacI+q0xP1GF3Ak |
| 34 |
=6VxI |
| 35 |
-----END PGP SIGNATURE----- |
Archives