Re: [Exim] Debian Package

トップ ページ
このメッセージを削除
このメッセージに返信
著者: Georg v. Zezschwitz
日付:  
To: Alex King
CC: exim-users, mark
新しいトピック: [Exim] Forced routes for specified domains, then use smarthost
題目: Re: [Exim] Debian Package
Hi Alex,

I totally agree with your opionion. However, this list is wrong.

As both a Debian user and an Exim user, I'm glad Debian chose
Exim as the default MTA, but the Exim list has really nearly
nothing to do with the Debian software selection.

For quite some time is was not even known "here", which
version of Exim is included in the Debian list. So please,
ask the package maintainer for these changes.

Cheers,


Georg

On Sat, Jan 13, 2001 at 02:30:55PM +1300, Alex King wrote:
> Speaking as a debian user, and an admin of quite a few debian systems,
> I would not like to see mysql drivers compiled in to the standard
> package. However I'm not so sure dynamically loaded libraries are the
> way to go either. Would the extra code, complexity, and possible new
> security problems be worth it? I suspect not.
>
> Is it possible to have different exim packages, eg exim-tiny, exim and
> exim-db, or is this discouraged by policy?
>
> exim-tiny could have a very minimal set of directors, routers and
> lookup types compiled in, and exim-db would have all possible drivers
> in and the regular package could stay as it is.
>
> Most of the systems I administer don't use any lookups at all except
> for an lsearch for the aliases file. I would use a deb with only
> lsearch compiled in if it were available, and I suspect this would do
> for 90% of debian users too.
>
> > I however want on-demand loading of modules from shared libraries for a
> > different reason.
> >
> > As the maintainer of the debian package of exim I get a lot of mails asking
> > me to compile in the mysql and/or pgsql lookup drivers (normally mysql - I
> > don't know why it's more popular than pgsql but it does seem to be). I would
> > like to; debian policy says that I should compile in all optional features
> > unless there is an over-riding reason not to.
> >
> > In this case there is what I consider to be an over-riding reason not to:
> > exim is a priority "important" package[1] and including those lookup drivers
> > woudl bring two big databases, or at very least their client libraries, into
> > important, which I don't want to do.
> >
> >
> > [1] Definition is summarised as "The important packages are just a bare
> > minimum of commonly-expected and necessary tools."
> >
>
> --
> ## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##