On Sat, 22 Sep 2012 14:48:38 -0700 Ross Boylan <r...@biostat.ucsf.edu> wrote:
> > Anyway, you can choose any of 3 approaches to configuration: > 1. Use the split config in conjunction with the package management > tools (debconf) to configure exim. > > 2. Like 1, but use the monolithic config file. It's not clear to if > changes you make in debconf, or that the package might make on > upgrade, will get integrated in to the monolithic file in this case. > Exim4 separated from debconf itself between, I think, etch and lenny. Any debconf material left in the configuration file then caused the installation of the new exim4 during the upgrade to die horribly, in a way that even dpkg couldn't fix. Guess who fell into that one. That was a mandatory 'use package maintainer's configuration', but I hadn't seen that coming, and made the wrong choice when it was offered. The exim4 dpkg configuration questionnaire now produces macro constants which are interpreted within the configuration file(s), so anything done here will generally be preserved across upgrades. With the single file, it is encouraged to make further customisations in terms of macro constants, and set these in exim.conf.localmacros, and if it is necessary to add new code, to do it in new files in the conf.d structure, having switched to 'split-file'. The ultimate aim is to leave the original configuration file/files untouched, with all user modifications made in user-created files, so that user customisations are completely untouched by upgrades (at least so far as no functional changes occur). I can appreciate the desire for this, having had to go through the old and new configuration files line by line to ensure sensible translation, after the problem I had during the upgrade. While I have not actually done a concatenation of the as-supplied split files and compared them to the monolithic one, nothing I have ever seen leads me to believe they would be different, apart from some comments. The section names and numbers in the monolithic file should allow a given bit of code to be found among the split files. The user macros are handled slightly differently, as exim.conf.localmacros is not used, but it shouldn't be hard to see how. I have to admit to using the single file, as I haven't yet had the enthusiasm to go through my old (sarge?) and heavily-customised one to break it into the bite-sized conf.d chunks. I've done a bit of it, removing my list of banned TLDs and placing it in a separate file, referred to by macro expansion. But there's a lot more to go, and if it ain't broke... -- Joe -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120923101620.49384...@jretrading.com
