On 2014-03-26 23:07:17 [+0100], Sebastian Andrzej Siewior wrote: > I think the whole debconf thingy got a little out of hand. Almost every > option in the config file can be changed. As you say, it adds complexity > atm. Maybe too much since we are now busy to get it bug free. > > I do get a little anxious if I want to change one option and have to > click my self carefully through the options so I don't get press enter > too often… That is maybe my own problem here. I don't use this on my > servers, just now for testing. > Anyway. What do we gain here exactly? What is the advantage of using debconf > for every config item over giving a sane default config with a comment over > each option? > I understand that for things like LogRotate it is pleasant that the > logrotate.d > file is automaticly created with the proper user for instance. However > this isn't working perfectly atm and I didn't find other example. The > other options seem to written to the config file as-is. > > Looking at apache, nginx, exim for instance they all ship a default > config which works and leave it up to the user to deal with it. Exim has > a few questions, true, but they mostly compare to what freshclam asks > and are way less compared to `base'. unbound gives a config file with a > lot of comments next to each option. That is what _I_ like. > > Said that I wouldn't mind if we drop the LogRotate option(s). I wouldn't > even mind if we drop them all. Well. freshclam has the usefull question > where you can choose between daemon, cron, and so on. I consider this > usefull.
gentle ping. > > Scott K Sebastian _______________________________________________ Pkg-clamav-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-clamav-devel
