[arch-general] dovecot.conf moved to dovecot.pacsave - why?
All, Why does the new dovecot package move the dovecot.conf to dovecot.conf.pacsave? The same 2.0 configuration works with 2.1, why leave the user without any dovecot.conf at all? [2012-02-27 15:17] warning: /etc/ssl/dovecot-openssl.cnf saved as /etc/ssl/dovecot-openssl.cnf.pacsave [2012-02-27 15:17] warning: /etc/dovecot/dovecot.conf saved as /etc/dovecot/dovecot.conf.pacsave [2012-02-27 15:17] upgraded dovecot (2.0.18-1 -> 2.1.1-3) Why not a just a warning that: warning: basic configuration options have been updated, see: http://wiki2.dovecot.org/BasicConfiguration -- David C. Rankin, J.D.,P.E.
On Tue, Feb 28, 2012 at 7:51 AM, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
Was just coming here to ask similar. As far as I can understand, this is so the user can use their own (unaffected by upgrades) dovecot.conf, but we have /etc/dovecot/local.conf which is by default enabled in the stock dovecot.conf anyway for that.
On 02/27/2012 06:18 PM, Oon-Ee Ng wrote:
I've been through the dovecot wiki and the config changes are not really relevant for simple installs. If you have some crazy multi-virtual-server setup with multiple TLS Server Name Indication setup, then maybe the /etc/dovecot/conf.d/##-udev-like-rules makes sense, but for simple TLS setups, dovecot.conf is a far better setup. For the simple case, the dovecot.conf still works fine, so I would argue against the move to dovecot.conf.pacsave by default. It's a minor thing, but as a packaging policy, unless the existing config will 'no longer work', then why disable it? -- David C. Rankin, J.D.,P.E.
On Tue, Feb 28, 2012 at 12:51 AM, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
If you wonder why a packaging change was made, the first place to look is in the changelogs: <http://projects.archlinux.org/svntogit/packages.git/log/trunk?h=packages/dovecot>.
From there you should hopefully find your answers :-)
HTH, Tom
On 02/27/2012 07:30 PM, Tom Gundersen wrote:
Tom, Thanks, that does help, but that just leave me with more questions. I'm might be reading it wrong, but what I get is: <quote> upgpkg: dovecot 2.1.1-3 don't install sample config files to /etc direclty, they break dovecot start way too often - FS#20809; add mkcert helper script </quote> That's fine and I agree. But, if we are not going to install the sample config, why does that mean we have to move the existing dovecot.conf to dovecot.conf.pacsave and leave the user without any config on existing installs? Maybe it's just a pacman limitation not knowing whether it is upgrading or installing for the first time, but isn't there a way in an install script to simply do a [[ -e /etc/dovecot/dovecot.conf ]] && "don't touch it" or [[ -e /etc/dovecot/dovecot.conf ]] && mv /etc/dovecot/dovecot.conf \ /etc/dovecot/local.conf Like I said earlier, this isn't a huge issue, but I was just looking for some better way to handle upgrades by keeping existing configs when they will still work and nuking them when they will fail cause a fail to start. I guess 'one size doesn't fit all' and there is really know way for pacman to know whether the existing config will still work or not. Even still, leaving the existing config in such situations still seems like the better policy. -- David C. Rankin, J.D.,P.E.
On Tue, Feb 28, 2012 at 10:34 AM, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
Its not done in an install script, previous to this version /etc/dovecot/dovecot.conf belong to the dovecot package. When it no longer belongs to said package it is moved to <name>.pacsave, this is reasonable pacman behaviour because there's no telling what the reason was for the file being removed. Its not a conscious "move this file" done in the update as you can see from the changelog/PKGBUILD.
On 02/27/2012 06:51 PM, David C. Rankin wrote:
For me when I updated to dovecot 2.1.1-3 it was even worse - or at least surprising ... It saved dovecot.conf as a .pacsave - but it also deleted every standard file in conf.d subdir except for the ones I changed - which were also moved to .pacsave. I think deleting all the config file violates the least surprise approach ... gene
participants (4)
-
David C. Rankin
-
Genes MailLists
-
Oon-Ee Ng
-
Tom Gundersen