On Wed, 2007-08-01 at 14:46 +0300, Timo Sirainen wrote:
On Wed, 2007-08-01 at 06:51 -0400, Bruce Bodger wrote:
This comment still remains in the dovecot-sieve "INSTALL"...
"It's also not a good idea to build the plugin against self-compiled
Dovecot sources, but then actually use a prebuilt binary package of Dovecot. That
might work if the Dovecot versions are the same, but it's not guaranteed."Being a Mac System, I've ALWAYS built dovecot-sieve against self- compiled Dovecot sources and have never had an issue with sieve (that
others also haven't had.) So maybe that comment is no longer
required? (For me, it's just confusing :-))I guess I could change "might work" -> "most likely works".
Or I guess since this hasn't been a problem normally I could just remove it unless it becomes a common problem. Updated the text:
Use --with-dovecot=<path> to point to dovecot-config file's directory. There are two possibilities where this could exist:
If you configured Dovecot with --enable-header-install, you'll have dovecot-config installed in $prefix/lib/dovecot/ directory.
Compiled Dovecot sources' root directory.
So for example:
./configure --with-dovecot=/usr/local/lib/dovecot make sudo make install
sievec and sieved binaries are built only if you use 2) method, because they need to link with Dovecot's libraries. They can be used to compile and decompile Sieve scripts. You probably don't need these.