| 1 |
On 08/13/2017 05:23 PM, M. J. Everitt wrote: |
| 2 |
> On 14/08/17 01:19, Zac Medico wrote [excerpted]: |
| 3 |
>> You'll get the same result as --autounmask-use-only if you use |
| 4 |
>> --autounmask-keep-keywords together with --autounmask-keep-masks. |
| 5 |
>> |
| 6 |
>> This way, we can also add --autounmask-keep-license and |
| 7 |
>> --autounmask-keep-use options if we want, and the meaning is very easy |
| 8 |
>> to explain. The meaning of --autounmask-use-only would have required |
| 9 |
>> more explanation, since it allowed license changes in addition to USE |
| 10 |
>> changes. |
| 11 |
> I guess that's the more flexible option, and logical to all users of all |
| 12 |
> locales ;) |
| 13 |
> |
| 14 |
> Does portage ignore missing command-line options, if I set them in my |
| 15 |
> make.conf in anticipation!?!?! |
| 16 |
|
| 17 |
No, unrecognized options are a fatal error. That's intentional, because |
| 18 |
having your settings ignored can harmful in some situations. |
| 19 |
|
| 20 |
> Thanks for the clear explanation, extra coding, and look forward to the |
| 21 |
> push to 'live' :) |
| 22 |
|
| 23 |
It's released in portage-2.3.7, so you can try it now. |
| 24 |
-- |
| 25 |
Thanks, |
| 26 |
Zac |
Archives