[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: handling moved configuration files
On Tue, Oct 26, 2010 at 08:12:22AM -0400, Greg Troxel wrote:
> Maybe it's better to convert it at once then (doveconf -n dovecot.conf >
> dovecot/dovecot.conf), if the old config exists and the new one doesn't.
> But I'm not aware of prior art for such things in pkgsrc.
> pgsql, which has big warnings to dump/restore and think hard. But mail
> should be simpler for users. If there is support to convert the config
> file, and we can script doing that and parking the old one in 20 lines
> of /bin/sh, I think that's a great approach.
Fair enough (but I'll wait for other opinions).
And I think the rc.d script is the better place then, rather than the
install script, so people can easily scratch the new config and start
over, without having to reinstall the package.
I can add an upgrade target to the rc.d script, automatically triggered by
a start_precmd if necessary (similar to sshd_keygen in base).
> Also I wonder at what point we could remove such logic then. After the
> next stable branch?
> That's vastly too soon. It's ok to remove the logic when the pain of
> keeping it outweighs the usefulness to people who have not yet upgraded.
> That's probably in 1.5-3 years.
Agreed. In the rc.d script it will not be much of a pain to keep it.
Geert Hendrickx -=- ghen%telenet.be@localhost -=- PGP: 0xC4BB9E9F
This e-mail was composed using 100% recycled spam messages!
Main Index |
Thread Index |