| 1 |
Zac Medico posted on Sun, 13 Aug 2017 19:27:53 -0700 as excerpted: |
| 2 |
|
| 3 |
> On 08/13/2017 07:00 PM, M. J. Everitt wrote: |
| 4 |
>> Interesting .. I'm sure I shied away from that option for some reason |
| 5 |
>> ... wonder if zmedico can shed some light on the difference between the |
| 6 |
>> new options and the old, apart from some added flexibility ... |
| 7 |
> |
| 8 |
> The --autounmask-keep-keywords option allows you to adjust the the way |
| 9 |
> that decisions are made during dependency resolution. |
| 10 |
|
| 11 |
> Changes in decision making behavior have a large impact on the resulting |
| 12 |
> dependency calculation. It can mean the difference between a successful |
| 13 |
> calculation, and one that produces useless results. |
| 14 |
> |
| 15 |
> The --autounmask-write=n option has no influence on the decisions made, |
| 16 |
|
| 17 |
> The --autounmask-keep-keywords option gives finer-grained control. This |
| 18 |
> finer-grained control is only useful in cases where --autounmask=n would |
| 19 |
> prevent useful configuration changes from being made. |
| 20 |
|
| 21 |
Thanks. Clear and succinct. |
| 22 |
|
| 23 |
That improved my own understanding as well, particularly the distinction |
| 24 |
between changing the decisions made, and not changing them, but simply |
| 25 |
preventing them being automatically written, allowing the user direct |
| 26 |
control over what's actually written and how. =:^) |
| 27 |
|
| 28 |
-- |
| 29 |
Duncan - List replies preferred. No HTML msgs. |
| 30 |
"Every nonfree program has a lord, a master -- |
| 31 |
and if you use the program, he is your master." Richard Stallman |
Archives