On 3/13/19 11:49 AM, Jason Tibbitts wrote:
> In general I agree with you, but for a distro the issue
> generally comes down to dependencies.
>
> In Fedora, for example, we split the virus scanning portion out to a
> separate package, because otherwise cyrus-imapd ends up with a
> dependency on cla
> "KM" == Ken Murchison writes:
KM> I don't see a downside to have one monolithic package. I think its
KM> easier for an admin to have everything available to them in one
KM> package rather than having to go find the correct package for the
KM> optional piece they are looking for.
In genera
Thanks, that helps. A couple of follow up questions:
I found this comment in the documentation for compiling cyrus-imapd:
MariaDB or MySQL development headers, to allow Cyrus IMAP to use
it as the backend for its databases.
Configure option: --with-mysql, --with-mysql-incdir,
--wi
I don't see a downside to have one monolithic package. I think its
easier for an admin to have everything available to them in one package
rather than having to go find the correct package for the optional piece
they are looking for. But that's just me.
On 3/12/19 12:39 PM, Patrick Goetz w
I'm finally getting around to updating the Arch linux cyrus-imapd
package, and have a question.
Looking through the configuration options, it looks like there are a
number of functionality critical decisions to be made:
CalDAV and CardDAV
./configure --enable-http --enable-calalarmd
Mu
