Cyrus may be configured to not support sieve, which lightens the server. Reproducible: Always Steps to Reproduce: 1. emerge cyrus-imapd 2. 3. Actual Results: Cyrus gets compiled and installed with sieve support Expected Results: Propose an option to disable sieve support The patch adds a local flags called "nosieve".
Created attachment 71277 [details, diff] Option to disable sieve support in cyrus Patch against cyrus-imapd-2.2.12-r3.ebuild; adds a "nosieve" local use flag to disable sieve support, installs pam file only if use pam enabled.
Oh no, not yet another evil no* flag. :/
I thought about that, but as sieve is historically enabled, it seemed the appropriate way... If a flag isn't specified, is it enabled or disabled ? Then I couuld change nosieve to "sieve", and only "-sieve" would drop support... Hmm, tests seem to show flag's disabled by default...
I am going to bump cyrus to 2.3.2 and thinking about adding this to it. Is there a reason you remove notifyd from SUBDIRS ? NOTIFYD(8) doesn't say anything about it has any relation with sieve. @@ -226,7 +230,14 @@ src_install() { dodir /usr/bin /usr/lib - for subdir in master imap imtest timsieved notifyd sieve; do + + if use nosieve; then + SUBDIRS="master imap imtest" + else + SUBDIRS="master imap imtest timsieved notifyd sieve" + fi + + for subdir in ${SUBDIRS}; do make -C "${subdir}" DESTDIR="${D}" install || die "make install failed" done
AFAIR, in Cyrus 2.2, notifyd wouldn't be built when sieve was disabled. Haven't tried again with 2.3 anyway.
dovecot using sieve use flag, have this in mind :)
Added as USE="sieve" in 2.3.13-r1.
