bug-mailutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-mailutils] Mailutils libsieve.so conflicts with libSieve


From: Sergey Poznyakoff
Subject: Re: [bug-mailutils] Mailutils libsieve.so conflicts with libSieve
Date: Tue, 03 Feb 2009 13:30:10 +0200

Hi Aaron,

> I'm the maintainer of libSieve, libsieve.sf.net, an implementation of the
> Sieve filtering language. libSieve installs as /usr/lib/libsieve.so.
> Unfortunately, so does GNU Mailutils' Sieve implementation.

Yes, indeed. That's an unfortunate coincidence.

> So between us we're going to have to work something out regarding library
> the name!

Certainly, we should solve this.

> I'm not sure where to begin on discussing this, but perhaps first I might
> ask how long mailutils has been installing a Sieve interpreter with the
> name "libsieve.so"?

It is installing it since version 0.1, which was released in
2002. And how long libSieve is using this name?

> Have we been avoiding a collision for a while because of different
> library versions?

Hardly, a symlink named libsieve.so is always created, no matter what the
version number. The only chance to avoid the collision would be to
install the two libraries in different directories (e.g. using
Mailutils' default installation prefix, which is /usr/local)... 

> Is it possible to rename Mailutils' libsieve.so to, say, libmu_sieve
> without breaking dependencies?

Well, I do not have any objections to renaming it, especially given that
the rest of Mailutils' libraries are already prefixed with `mu_'. This
could, however, cause problems when upgrading existing Mailutils
installations, because it will require relinking all programs that use
Mailutils Sieve implementation, which is not normally needed when
upgrading shared libraries.

Please, allow me some time to consider it. I'll get back to you in a
couple of days.

Regards,
Sergey




reply via email to

[Prev in Thread] Current Thread [Next in Thread]