On Thu, 2009-06-25 at 15:43 +0200, Edgar Fuß wrote: > The preferred way (for pkgsrc) would be if both Sieve and ManageSieve > could be built as stand-alone packages and not needing a dovecot > source tree to build. What's the long-term plan for Sieve/ManageSieve > in this respect? The pkgsrc infrastructure (intentionally) doesn't > like a package depending on anothers package working directory in > order to build. So with these cross-dependencies, the only pkgsrc ways > to go would be either to build it all as one package with options > (that's what I currently do) or extract, patch, configure and build > dovecot inside a sieve package.
Dovecot v2.0 installs shared libraries, which are used by Dovecot binaries and can also be used for building Sieve binaries. v2.0 isn't anywhere close to release, but you could already try and see if it provides everything that's necessary to do a clean pkgsrc.
signature.asc
Description: This is a digitally signed message part
