| 1 |
Zac Medico posted on Fri, 01 Jul 2016 08:35:26 -0700 as excerpted: |
| 2 |
|
| 3 |
>> But if you genuinely think this is a good idea, and someone else on the |
| 4 |
>> team does too, I won't oppose it. We should make sure that we strongly |
| 5 |
>> discourage its usage for regular users. Perhaps your suggested manpage |
| 6 |
>> addition already does -- I don't know. |
| 7 |
> |
| 8 |
> Yeah, I think the warning message that I've put in the man patch is |
| 9 |
> pretty good: |
| 10 |
> |
| 11 |
>> This option is intended to be used only with great caution, |
| 12 |
>> since it is possible for it to make nonsensical configuration changes |
| 13 |
>> which may lead to system breakage. Therefore, it is advisable to use |
| 14 |
>> ---ask together with this option. |
| 15 |
|
| 16 |
Perhaps rename the option so it makes perfectly clear the possible |
| 17 |
consequences? Something like --autounmask-breakme, or --auto-breakme ? |
| 18 |
|
| 19 |
Or alternatively, if there are other arguably dangerous options now or |
| 20 |
possible in the future, put them all under another option, --breakme, |
| 21 |
such that if that option isn't there, the otherwise dangerous options |
| 22 |
only print a warning and die. |
| 23 |
|
| 24 |
Then people can read the manpage if they really want to know what it |
| 25 |
does, but people who haven't, aren't as likely to blunder into it due to |
| 26 |
the stereotypical "rm -rf .*" type advice. |
| 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