| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 13/08/14 18:45, Brian Dolbec wrote: |
| 5 |
> Actually, re-reading your patches again, your patches actually made |
| 6 |
> more sense to me finally. You were fixing it to make implied |
| 7 |
> behavior the actual behavior. So while I was originally objecting |
| 8 |
> to them, then was not opposing them (last time we discussed |
| 9 |
> inclusion), I now see them much clearer and agree with them. |
| 10 |
> |
| 11 |
> The --ask implying --autounmask-write is something people would not |
| 12 |
> object to so strongly like they did to your original patchset. |
| 13 |
Let's merge the bug fix (see the other thread) first. I can still |
| 14 |
prepare the other patches if you think that's worthwhile, but I prefer |
| 15 |
keeping them separated from that very simple bugfix patch. |
| 16 |
|
| 17 |
|
| 18 |
One thing that needs discussion is what to do with the current |
| 19 |
behaviour of --autounmask, i.e. printing the suggestions. One thing |
| 20 |
that was really weird in my original patches (the ones in this thread) |
| 21 |
is this: |
| 22 |
|
| 23 |
emerge foo # this will do what --autounmask does today |
| 24 |
emerge foo --autounmask # this will do what --autounmask-write does |
| 25 |
emerge foo -a # this will do what --ask --autounmask-write does |
| 26 |
emerge foo --autounmask=n # this will do what --autounmask=n does |
| 27 |
|
| 28 |
The problem here is that there is no way to do e.g. emerge foo --ask, |
| 29 |
and get suggestions any longer. You can either have it prompt to write |
| 30 |
stuff, or you can have it not do anything -- but you can't explicitly |
| 31 |
have it suggest stuff without prompting to write. This is bad design. |
| 32 |
|
| 33 |
So either I need to implement tri-state (--autounmask can be yes, no, |
| 34 |
suggest), or I need to do something more drastic. |
| 35 |
|
| 36 |
Suggestions welcome. |
| 37 |
- -- |
| 38 |
Alexander |
| 39 |
bernalex@g.o |
| 40 |
https://secure.plaimi.net/~alexander |
| 41 |
-----BEGIN PGP SIGNATURE----- |
| 42 |
Version: GnuPG v2 |
| 43 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 44 |
|
| 45 |
iF4EAREIAAYFAlPrmLwACgkQRtClrXBQc7UBaQEAmdDIIApMb99GIM2UnPHmH6c2 |
| 46 |
IvuVynLLfbprR2WjdnEA/0czubzAIeGJPCbhQvEoHyb2BC3KSzWThaQVYFrvt05D |
| 47 |
=5lOp |
| 48 |
-----END PGP SIGNATURE----- |
Archives