Precedence: list
MIME-Version: 1.0
In-Reply-To: <1489489894.11710.552.camel@gmail.com>
References: <20170310091712.18974-1-valery.kartel@gmail.com> <1489489894.11710.552.camel@gmail.com>
From: Valery Kartel <valery.kartel@gmail.com>
Date: Tue, 14 Mar 2017 13:32:20 +0200
Message-ID: <CAKTwcDM0yZ0BqnQhbHv9AxW2W6xEj1Oj7ySG+FWUOHy-Cby_8w@mail.gmail.com>
Subject: Re: [alpine-aports] [PATCH v3] testing/exim: upgrade to 4.89
To: Leonardo Arena <rnalrd@gmail.com>
Cc: alpine-aports <alpine-aports@lists.alpinelinux.org>, Jesse Young <jlyo@jlyo.org>
Content-Type: multipart/alternative; boundary=94eb2c190e8058a273054aaf2eb4

--94eb2c190e8058a273054aaf2eb4
Content-Type: text/plain; charset=UTF-8

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

--94eb2c190e8058a273054aaf2eb4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>Hi,<br><br><span id=3D"gmail-result_box" class=
=3D"gmail-short_text" lang=3D"en"><span class=3D"gmail-">I suggest this ren=
aming because these subpackages are just lookup-backends (not scripts, util=
s etc...)</span></span><span id=3D"gmail-result_box" class=3D"gmail-short_t=
ext" lang=3D"en"><span class=3D"gmail-"><br><br>lsearch, dsearch, passwd - =
are file-based lookups. If I use sql database as storage I don&#39;t need t=
hose lookups at all.<br>So I propose this ability as an option (install exi=
m-server instead of exim)<br><br>Other distros usually have a monolitic exi=
m package.</span></span><br><span id=3D"gmail-result_box" class=3D"gmail-sh=
ort_text" lang=3D"en"><span class=3D"gmail-"></span></span></div></div><spa=
n id=3D"gmail-result_box" class=3D"gmail-short_text" lang=3D"en"><span clas=
s=3D"gmail-">A quick search in ubuntu I see exim4-base, exim4-config, and 2=
 varians of install: exim4-light &amp; exim4-heavy<br></span></span></div><=
div class=3D"gmail_extra"><br><div class=3D"gmail_quote">2017-03-14 13:11 G=
MT+02:00 Leonardo Arena <span dir=3D"ltr">&lt;<a href=3D"mailto:rnalrd@gmai=
l.com" target=3D"_blank">rnalrd@gmail.com</a>&gt;</span>:<br><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">Hi!<br>
<span class=3D""><br>
On ven, 2017-03-10 at 11:17 +0200, Valery Kartel wrote:<br>
&gt; - APKBUILD cleanups and improve redability<br>
&gt; - add redis lookup backend support<br>
&gt; - rewrite lookup backends building in APKBUILD<br>
&gt; - rename lookup backends subpackages to exim-lookup_$backend<br>
&gt; =C2=A0 and make it provides its old exim-$backend subpackages name.<br=
>
&gt;<br>
<br>
</span>I don&#39;t get why it was needed to rename. How other distros namin=
g it?<br>
Other MTAs packages like postfix use $pkgname-$backend. Am I missing<br>
something?<br>
<span class=3D""><br>
&gt; ---<br>
&gt; v1 -&gt; v2: remade exim-lookup_pgsql to provide compatibility<br>
&gt; =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0name exim-=
postgresql and remove exim-postgresql subpackage.<br>
&gt;<br>
&gt; v2 -&gt; v3: - move lsearch, dsearch, passwd to modules<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0=C2=A0- make pure &#39;server&#39; pac=
k (just exim-binary, config, init<br>
&gt; scripts)<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0=C2=A0- exim package now depends on ex=
im-server, minimal set of<br>
&gt; lookups<br>
<br>
</span>If the server needs=C2=A0lsearch, dsearch, passwd modules to run, wh=
at is<br>
the benefit of making subpackages? Is there a usage case where you need<br>
only the lookup tools, perhaps with the utils? I see that exim-utils<br>
pulls in the server package anyway.<br>
<br>
Thanks!<br>
<br>
|_eo</blockquote></div><br></div>

--94eb2c190e8058a273054aaf2eb4--


---
Unsubscribe:  alpine-aports+unsubscribe@lists.alpinelinux.org
Help:         alpine-aports+help@lists.alpinelinux.org
---