Here's what I do to install on a Fedora 4 system with sendmail:

1. tar -zxvf dovecot-1.0.alpha4.tar.gz
2. cd dovecot-1.0.alpha4
3. ./configure --with-pop3d --with-passwd --with-shadow
4. make
5. make install
6. edit the dovecot.conf
7. create the /usr/local/var directory
8. add a dovecot group and user
9. and finally, add /usr/local/sbin/dovecot to /etc/rc.d/rc.local so that it starts on reboot

I'm thinking the install must have put dovecot in /usr/local/sbin because I don't remember putting it there. I see two dovecot files in /usr/local/sbin: dovecot & dovecotpw. So, if I understand you correctly, you are saying I can move those files and create symbolic links to them. What if I just rename them and give them an extension of .alpha4 so that they won't be used after I install alpha5? Then, just do a couple of renames if I have to fall-back. However, I don't think those are the only 2 files dovecot uses when executing (I also see pop3 running often).

Cliff

-----Original Message----- From: dovecot-bounces@dovecot.org [mailto:dovecot-bounces@dovecot.org]On Behalf Of Andy Cravens Sent: Tuesday, December 13, 2005 10:29 PM To: dovecot@dovecot.org Subject: Re: [Dovecot] Best way to upgrade from 1.0a4 to 1.0a5

It depends on if you are compiling from source or using an rpm or other package manager? If you compile from source you can select the desired install directory.

Personally, I install under /opt/dovecot-version and then make a symbolic link named /opt/dovecot which points to the version I'm currently using. All my startup/shutdown scripts look at /opt/dovecot

If you plan on upgrading often, it's a good idea to keep several versions of the software on hand in case you have to go back.

I just upgraded today. All I had to do was compile and install in /opt/dovecot-1.0alpha5, delete the existing symbolic link and repoint to /opt/dovecot-1.0alpha5 and restart dovecot. To switch back you just point the symbolic link back to the old directory and restart dovecot. Takes less than 10 seconds to switch versions if you type fast.

Of course, it's a good idea to check the release notes to make sure your existing config file will work with the newer version. I had a minor problem going from alpha3 to alpha4 because of a config problem. I was able to switch back quickly and correct the problem and then go forward again.

On 12/14/2005, "Cliff Hayes" <chayes@afo.net> wrote:

Hello all,

I have 1.0 Alpha 4. Is it better to shut down sendmail, uninstall dovecot 1.0a4 then install 1.0a5, or just install 1.0a5 over the top of 1.0a4?

Thanks,

Clif

Andy,

I'll take your word for it. I can't find those configure options in the documentation.

Cliff

-----Original Message----- From: dovecot-bounces@dovecot.org [mailto:dovecot-bounces@dovecot.org]On Behalf Of Andy Cravens Sent: Wednesday, December 14, 2005 10:15 AM Cc: dovecot@dovecot.org Subject: Re: [Dovecot] Best way to upgrade from 1.0a4 to 1.0a5

Cliff... you need to specify the install directory when you configure. I would recommend including the version number in the directory name to make it easier to keep track of versions. I also place the config file in a "shared" directory like /etc so I can use the same config file for any version. Again, you have to make sure there are no config incompatabilities between versions before you switch. Here's what I did on a Solaris host but you should be able to do this on Fedora. Common file locations may be different on Linux vs. Solaris hosts but the idea is the same.

Example installing under /opt options here as needed for your install)

1. ./configure --prefix=/opt/dovecot-1.0.a5 --sysconfdir=/etc (add other

2. make
3. make install
4. cd /opt
5. ln -s dovecot-1.0a5 dovecot
6. edit your start/stop scripts to look at /opt/dovecot and NOT /opt/dovecot-1.0a5

Then, to change versions you just do:

1. cp /etc/dovecot.conf /etc/dovecot.conf.backup (backup the conf file)
2. cd /opt
3. rm dovecot
4. ln -s dovecot-1.0.a6 dovecot (notice I put aplha6 only as an example)
5. /etc/init.d/dovecot restart (Restart script would be different on linux)

The advantage to doing it this way is that you have a complete installation of each version. The only thing I change between versions is the symbolic link /opt/dovecot. Once I'm sure I won't be going back to the old version I will delete the old directory.

Cliff Hayes wrote:

Here's what I do to install on a Fedora 4 system with sendmail:

1. tar -zxvf dovecot-1.0.alpha4.tar.gz
2. cd dovecot-1.0.alpha4
3. ./configure --with-pop3d --with-passwd --with-shadow
4. make
5. make install
6. edit the dovecot.conf
7. create the /usr/local/var directory
8. add a dovecot group and user
9. and finally, add /usr/local/sbin/dovecot to /etc/rc.d/rc.local so that it starts on reboot

I'm thinking the install must have put dovecot in /usr/local/sbin because I don't remember putting it there. I see two dovecot files in /usr/local/sbin: dovecot & dovecotpw. So, if I understand you correctly, you are saying I can move those files and create symbolic links to them. What if I just rename them and give them an extension of .alpha4 so that they won't be used after I install alpha5? Then, just do a couple of renames if I have to fall-back. However, I don't think those are the only 2 files dovecot uses when executing (I also see pop3 running often).