> I think, as other debian package, only files with a specific extension
> have to be read (*.conf?)
That sounds like a big diversion from upstream, since none of the
current files in that directory contain an extension. The result of this
could be that the various tutorials/howtos on the web can't be applied
to Debian any more.
FreeRADIUS 3 (not in Debian) uses a folder mods-enabled, similar to
sites-enabled. I guess this is the cleanest solution, but backporting it
to v2.x will result in different problems.
> or at least that sources of trouble have to be added to debian
> documentation (README.Debian and something like that).
That sounds less intrusive. Maybe another option is to warn in the logs,
or even fail to start, if a file with a name matching
.{dpkg,ucf}-{dist,new} is encountered (I've got no idea what the
preferred option here should be).
--
Herwin Weststrate
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
