Josip Rodin wrote:
On Sat, Jul 29, 2006 at 11:34:16AM -0400, Andres Salomon wrote:
As I mentioned on IRC, I really don't see the point of having two
maildrops in Debian. Why do we need both maildrop and courier-maildrop?
It seems that Stefan custom-tailored courier-maildrop, whose description
states:
The installation of this package is recommended only for using it in
conjunction with the sqwebmail package. Please use the standalone maildrop
package otherwise.
Compared to the current maildrop 2.x package (in experimental), the
dependencies only differ in the fact that the courier-maildrop package
depends on courier-base, while maildrop has a plugin for courier-authlib.
There's also a libfam0 dependency in courier-maildrop, but it's not
immediately obvious to me what it could be for.
Fam is optional and from the maildirwatch.h source-code:
** These function leverage libfam.a to watch for maildir changes.
Yet it doesn't seem that the FAM provided functions are used.
For example: maildirwatch_check() is defined but never used. Likewise
with maildirwatch_started() and maildirwatch_end().
I think we can safely drop the libfam dependency.
It's about time that maildrop 2.0 gets included in unstable. Maildrop
1.5 is obsolete and using the authlib removes the need for a maildrop
specific config file like maildropmysql.config
The versioning scheme is clearly different.
Once maildrop 2.x is in unstable/testing, could it be possible to make
courier-maildrop ony a set of scripts that tune maildrop proper, and depend
on it?
It seems that sqwebmail depends on authlib too. So let's make one
maildrop depending on authlib.
Kind regards,
Jasper
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
