Aaron Stone wrote:
On Thu, 2006-08-17 at 01:34 -0400, Matthew T. O'Connor wrote:
We need better (more? some?) Sieve documentation. libSieve is hard to
install (running CentOS, probably easier on debian), and it's hard to
figure out how to use after you have it.
It shouldn't be much harder than ./configure ; make ; make install
As a library, there are no frontend programs that come with it. So once
installed, it's just kinda there, waiting to be linked to. Did you run
into any complications during the build process?
If there aren't any more issues that come up with libSieve 2.1.3, I'm
going to release just the code portion of the tarball as 2.2.0 --
leaving out the www and rfc directories -- so I do greatly appreciate
any bug reports, complaints, ideas to round out the library.
Well, here are the issues I ran into. Compiling libSieve wasn't the
hard part, I did ./configure --prefix=/usr/local/libsieve && make &&
make install and that worked fine. The hard part was then getting
DBMail to compile with libsieve, I used:
./configure --prefix=/usr/local/dbmail --with-pgsql
--with-sieve=/usr/local/libsieve/include
This got me through configure but then make failed to find the header
files, or the libraries, so I had to simlink the libraries to the system
library directory (/usr/lib) and symlink the header files into the
DBMail source directory.
What might be helpful is if libsieve created a pkgconfig file like gmime
does, that way the compiler can easily be told where everything is.
Thoughts?
Check out www.sieve.info -- it's the home site for the Sieve language.
Ahh... That is what I have been looking for, didn't come up in my google
search. We definitely need a link to this on the wiki or in the Sieve
docs or both.
Thanks again, Sieve ROCKS!
