[Dovecot] How do I test new code?

[Timo Sirainen]

On Thu, 2007-06-14 at 11:27 -0400, Stewart Dean wrote:
> I know how to run a second instance of the *base* code (to check 
> different functionality/config) and documented it in
> http://wiki.dovecot.org/RunningDovecot
> 
> What I realize I don't know how to do is to run an altogether different 
> version or build of the code as that second instance, which would be 
> good to have to check out upgrades before they go into production.  
> While I could do a build in the regular fashion and put DC somewhere 
> else or name it something else, so I could invoke this different code, 
> presumably that different code will still look for the subsidiary 
> executables in the usual place.  Do I have to change the DESTDIR parm 
> when doing the make install or some such? 

./configure --prefix=/another/dovecot/installation

> I do realize that,  just as I did with running a second instance of the 
> *same* code, I'd have to change the config file, have a separate 
> /var/run directory......

If you use --prefix all the default paths are changed, so you can leave
base_dir etc. as defaults.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://dovecot.org/pipermail/dovecot/attachments/20070614/b5c6cc50/attachment.bin