.rpmnew files during RPM upgrade

[Phil Mayers]

On 11/09/12 12:16, Phil Mayers wrote:
>
> Change the modules directory to a locally-managed one:
>
> $INCLUDE modules-active/
>
> ...and symlink from there to the files in the rpm-managed directory, or edit locally as needed.

(In more length now that I'm back at my desk)

This approach of a separate available/enabled modules dir is the default 
approach in the MASTER branch (to be 3.x):

https://github.com/alandekok/freeradius-server/blob/master/raddb/radiusd.conf.in#L760

I don't think blacklisting specific extensions in the conffile.c source 
is helpful, personally. It's "magic" and hardcoded lists are a pain - 
what seems reasonable to one person can be annoying to another.

You could possibly extend the syntax to be a glob e.g.

$INCLUDE mods/*.mod

...but the default would need to stay as-is in the 2.x branch for 
backwards compatibility. Possibly you could persuade people to change 
all the $INCLUDE'ed files to have relevant extensions e.g.

modules/mschap.mod
sites-enabled/inner-tunnel.vserver

...but they seem like "noise" to me. I like the separate dir / symlink 
approach.