| 1 |
On 03/24/2018 01:33 PM, Kent Fredric wrote: |
| 2 |
> On Sat, 24 Mar 2018 11:27:20 -0700 |
| 3 |
> Zac Medico <zmedico@g.o> wrote: |
| 4 |
> |
| 5 |
>> The defaults certainly do not work perfectly in all situations. However, |
| 6 |
>> there are a vast number of situations where using --autounmask-continue |
| 7 |
>> will make appropriate package.mask changes without the need for any user |
| 8 |
>> intervention. |
| 9 |
> |
| 10 |
> Its really handy for use flags. |
| 11 |
> |
| 12 |
> Its really handy for mixed arch/~arch where it promotes arch to ~arch as needed. |
| 13 |
> |
| 14 |
> Its really really bad however to have a default of accepting ** and |
| 15 |
> package.unmask as a primary go-to solution. |
| 16 |
|
| 17 |
That only happens when dependency satisfaction fails by normal means. |
| 18 |
|
| 19 |
> That default gets people using broken openssl and experimental packages |
| 20 |
> blindly without them ever having intended on getting into experimental |
| 21 |
> waters. |
| 22 |
|
| 23 |
If people can't be bothered to understand the meaning of package.mask |
| 24 |
and keywords changes, should they really be using Gentoo? |
| 25 |
-- |
| 26 |
Thanks, |
| 27 |
Zac |
Archives