| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 13/08/14 19:59, Duncan wrote: |
| 5 |
> * I don't want portage writing mask/use changes on its own under |
| 6 |
> any circumstances, as I use directories and have my own idea of |
| 7 |
> what files I want stuff in. |
| 8 |
It never has, and these patches never have implemented this. You |
| 9 |
raised the same concerns a year ago, and they did not make sense then |
| 10 |
either. |
| 11 |
|
| 12 |
> The patches as they are now would change that, giving me no way to |
| 13 |
> still get the suggestions with --ask, without chancing the actual |
| 14 |
> write of those changes. |
| 15 |
The patches do not do that. |
| 16 |
|
| 17 |
> The only other /possible/ objection I see is the potential |
| 18 |
> version- dependent confusion over --autounmask behavior. |
| 19 |
This is one of the reasons I am kind of neutral on applying them at |
| 20 |
all at this point. |
| 21 |
|
| 22 |
> But I don't feel strongly about that. |
| 23 |
Me neither. |
| 24 |
- -- |
| 25 |
Alexander |
| 26 |
bernalex@g.o |
| 27 |
https://secure.plaimi.net/~alexander |
| 28 |
-----BEGIN PGP SIGNATURE----- |
| 29 |
Version: GnuPG v2 |
| 30 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 31 |
|
| 32 |
iF4EAREIAAYFAlPrsN8ACgkQRtClrXBQc7W1HgEApAThYm9jvpGDOeoczC67/3eY |
| 33 |
ORcLtHG2c6UGoI3mwhgBALHfnxR4qJk19c8KeDK4H7d/9+g0O45ZAr/Gdo5Wf2z5 |
| 34 |
=l15a |
| 35 |
-----END PGP SIGNATURE----- |
Archives