[Dovecot] How do I test new code?
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? 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.. -- Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 [EMAIL PROTECTED] voice: 845-758-7475, fax: 845-758-7035
Re: [Dovecot] How do I test new code?
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. signature.asc Description: This is a digitally signed message part
