| 1 |
On Sat, 24 Mar 2018 11:27:20 -0700 |
| 2 |
Zac Medico <zmedico@g.o> wrote: |
| 3 |
|
| 4 |
> The defaults certainly do not work perfectly in all situations. However, |
| 5 |
> there are a vast number of situations where using --autounmask-continue |
| 6 |
> will make appropriate package.mask changes without the need for any user |
| 7 |
> intervention. |
| 8 |
|
| 9 |
Its really handy for use flags. |
| 10 |
|
| 11 |
Its really handy for mixed arch/~arch where it promotes arch to ~arch as needed. |
| 12 |
|
| 13 |
Its really really bad however to have a default of accepting ** and |
| 14 |
package.unmask as a primary go-to solution. |
| 15 |
|
| 16 |
That default gets people using broken openssl and experimental packages |
| 17 |
blindly without them ever having intended on getting into experimental |
| 18 |
waters. |
Archives