This bug says: "SWAT should not remove "security = user" even if it is
implied and the default.  This makes the setup confusing and error
prone."

I actually beg to disagree. SWAT has always been "sold" as a tool
that's likely to rewrite the configuration file. So, if the user wants
to maintain the configuration file outside SWAT, (s)he should not use
SWAT at all..:-)

The user is here requesting that swat reads all settings from a
configuration file and then rewrites them in the config file even if
they have their default value....

I don't really think this is what SWAT is really meant for...the
point, for me, is more keeping only the settings that *do not* have
their default value.

Attachment: signature.asc
Description: Digital signature

Reply via email to