Re: [Shorewall-users] Shorewall 4.4.20.1

[Simon M. <sim...@in...>]

> On 6/7/11 6:55 AM, Simon Matter wrote:
>>> There has been some dissatisfaction expressed with my decision to merge
>>> manpage documentation into the configuration files by default. So I'm
>>> releasing 4.4.20.1 that switches the default to not include
>>> documentation. If you do want the documentation, supply the -a
>>> (annotate) option to the installer.
>>
>> Hi Tom,
>>
>> I'd be interested to hear what kind of "dissatisfaction" was expressed
>> to
>> you? I have welcomed the change because it eliminates most man page
>> lookups for me. That said, I'm using some kind of diff/patch magic to
>> keep
>> the configs on my systems up2date. I can understand that otherwise the
>> docs in the configs would become out of date.
>
> First, it is a departure from my long-standing practice of not changing
> the default behavior.
>
> Second, the issue of the documentation becoming out of date is a real
> concern. I have plans to eliminate that problem by optionally allowing
> the existing files to be merged with the latest manpages during upgrade.
> See Mr Dash Four's post on the development list where he demonstrated a
> limited such a facility for shorewall.conf.

OK, what I do is not limited to shorewall, I do in with every RPM update.
What I do is to create a backup file named .orig before editing any config
file. Then, RPM will create a .rpmnew file, and the config update script
does all the diffing and patching so the .orig and the real config get
updated. I don't know how to keep configs clean otherwise.

Simon