Hi!
On ven, 2017-03-10 at 11:17 +0200, Valery Kartel wrote:
> - APKBUILD cleanups and improve redability> - add redis lookup backend support> - rewrite lookup backends building in APKBUILD> - rename lookup backends subpackages to exim-lookup_$backend> and make it provides its old exim-$backend subpackages name.>
I don't get why it was needed to rename. How other distros naming it?
Other MTAs packages like postfix use $pkgname-$backend. Am I missing
something?
> ---> v1 -> v2: remade exim-lookup_pgsql to provide compatibility> name exim-postgresql and remove exim-postgresql subpackage.> > v2 -> v3: - move lsearch, dsearch, passwd to modules> - make pure 'server' pack (just exim-binary, config, init> scripts)> - exim package now depends on exim-server, minimal set of> lookups
If the server needs lsearch, dsearch, passwd modules to run, what is
the benefit of making subpackages? Is there a usage case where you need
only the lookup tools, perhaps with the utils? I see that exim-utils
pulls in the server package anyway.
Thanks!
|_eo
Hi,
I suggest this renaming because these subpackages are just lookup-backends
(not scripts, utils etc...)
lsearch, dsearch, passwd - are file-based lookups. If I use sql database as
storage I don't need those lookups at all.
So I propose this ability as an option (install exim-server instead of exim)
Other distros usually have a monolitic exim package.
A quick search in ubuntu I see exim4-base, exim4-config, and 2 varians of
install: exim4-light & exim4-heavy
2017-03-14 13:11 GMT+02:00 Leonardo Arena <rnalrd@gmail.com>:
> Hi!>> On ven, 2017-03-10 at 11:17 +0200, Valery Kartel wrote:> > - APKBUILD cleanups and improve redability> > - add redis lookup backend support> > - rewrite lookup backends building in APKBUILD> > - rename lookup backends subpackages to exim-lookup_$backend> > and make it provides its old exim-$backend subpackages name.> >>> I don't get why it was needed to rename. How other distros naming it?> Other MTAs packages like postfix use $pkgname-$backend. Am I missing> something?>> > ---> > v1 -> v2: remade exim-lookup_pgsql to provide compatibility> > name exim-postgresql and remove exim-postgresql subpackage.> >> > v2 -> v3: - move lsearch, dsearch, passwd to modules> > - make pure 'server' pack (just exim-binary, config, init> > scripts)> > - exim package now depends on exim-server, minimal set of> > lookups>> If the server needs lsearch, dsearch, passwd modules to run, what is> the benefit of making subpackages? Is there a usage case where you need> only the lookup tools, perhaps with the utils? I see that exim-utils> pulls in the server package anyway.>> Thanks!>> |_eo
Hi,
On 14/03/2017 12:32, Valery Kartel wrote:
> Hi,> > I suggest this renaming because these subpackages are just> lookup-backends (not scripts, utils etc...)>
Yes, but also postfix has the same subpackages for the same purpose and
they aren't prefixed by "lookup". I'd just keep naming $pkgname-$backend.
> lsearch, dsearch, passwd - are file-based lookups. If I use sql database> as storage I don't need those lookups at all.> So I propose this ability as an option (install exim-server instead of exim)>
This sounds good.
Thanks!
|_eo
Hi,
2017-03-23 17:36 GMT+02:00 Leonardo Arena <rnalrd@gmail.com>:
>> Yes, but also postfix has the same subpackages for the same purpose and> they aren't prefixed by "lookup". I'd just keep naming $pkgname-$backend.>
It's a postfix's internal problem :)
All those lookup_backends provides their legacy names.
$ apk search exim-lsearch exim-redis
exim-lookup_redis-4.89-r0
exim-lookup_lsearch-4.89-r0
And with this naming we have an easy way to view what lookups exim support
$apk search exim-lookup
exim-lookup_pgsql-4.89-r0
exim-lookup_cdb-4.89-r0
exim-lookup_dnsdb-4.89-r0
exim-lookup_passwd-4.89-r0
exim-lookup_lsearch-4.89-r0
exim-lookup_redis-4.89-r0
exim-lookup_dsearch-4.89-r0
exim-lookup_dbmdb-4.89-r0
exim-lookup_sqlite-4.89-r0
exim-lookup_mysql-4.89-r0