Precedence: list
MIME-Version: 1.0
From: C H <flydinslip@gmail.com>
Date: Thu, 7 Mar 2019 07:21:27 -0500
Message-ID: <CACYPpV98axeQ9DE0V6K84UjBxmcUdjJRrp3phxLWbsfNs2zUMQ@mail.gmail.com>
Subject: [alpine-devel] How to offer different configurations of a package
To: alpine-devel@lists.alpinelinux.org
Content-Type: multipart/alternative; boundary="000000000000f82af40583802578"

--000000000000f82af40583802578
Content-Type: text/plain; charset="UTF-8"

All-

I'm looking for some guidance on how best to define an APKBUILD file for an
already-supported package that I need modified.

Recent versions of ISC DHCP (package 'dhcp') support an LDAP-based
back-end, though it's disabled by default. Enablement requires adding a
pair of dependencies and two additional arguments to the configure script;
everything else remains unchanged. Easy enough.

If I were to offer my changes back to the community, how should this flavor
of the package be named? It seems less than ideal to have two very similar
packages in the tree; is there a convenient restructuring within the
APKBUILD file that would allow the two forms (with and without LDAP
support)? If not, so much within the build system seems to depend on
pkgname -- of which a 'dhcp' is defined. I'm not sure how best to proceed
in this case. I'm also not fully convinced that changing the existing
package is the right thing to do; I suspect there are folks who don't want
LDAP support.

If there are examples among existing packages I could use as templates I'm
happy to replicate.

As an aside, this issue may repeat when I reach Bind; quick checks suggest
I'll want to make configuration changes there too..

Thanks!

--000000000000f82af40583802578
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div dir=3D"auto">All-</div><div dir=3D"auto"><br></div><=
div dir=3D"auto">I&#39;m looking for some guidance on how best to define an=
 APKBUILD file for an already-supported package that I need modified.</div>=
<div dir=3D"auto"><br></div><div dir=3D"auto">Recent versions of ISC DHCP (=
package &#39;dhcp&#39;) support an LDAP-based back-end, though it&#39;s dis=
abled by default. Enablement requires adding a pair of dependencies and two=
 additional arguments to the configure script; everything else remains unch=
anged. Easy enough.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto=
">If I were to offer my changes back to the community, how should this flav=
or of the package be named? It seems less than ideal to have two very simil=
ar packages in the tree; is there a convenient restructuring within the APK=
BUILD file that would allow the two forms (with and without LDAP support)? =
If not, so much within the build system seems to depend on pkgname -- of wh=
ich a &#39;dhcp&#39; is defined. I&#39;m not sure how best to proceed in th=
is case. I&#39;m also not fully convinced that changing the existing packag=
e is the right thing to do; I suspect there are folks who don&#39;t want LD=
AP support.</div><div dir=3D"auto"><br></div><div dir=3D"auto">If there are=
 examples among existing packages I could use as templates I&#39;m happy to=
 replicate.</div><div dir=3D"auto"><br></div><div dir=3D"auto">As an aside,=
 this issue may repeat when I reach Bind; quick checks suggest I&#39;ll wan=
t to make configuration changes there too..</div><div dir=3D"auto"><br></di=
v><div dir=3D"auto">Thanks!</div><div dir=3D"auto"><br></div></div>

--000000000000f82af40583802578--


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---