Precedence: list
MIME-Version: 1.0
From: C H <flydinslip@gmail.com>
Date: Wed, 6 Mar 2019 23:36:51 -0500
Message-ID: <CACYPpV_4mFY-uSBVu-dBO21qQep48hVQYpw=CcT8smjMmub5Jw@mail.gmail.com>
Subject: [alpine-devel] How to offer different configurations of DHCP
To: alpine-devel@lists.alpinelinux.org
Content-Type: multipart/alternative; boundary="0000000000005d302c058379a849"

--0000000000005d302c058379a849
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.

Thanks!

--0000000000005d302c058379a849
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">All-<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 al=
ready-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 disabled by default. Enable=
ment requires adding a pair of dependencies and two additional arguments to=
 the configure script; everything else remains unchanged. Easy enough.=C2=
=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">If I were to offer m=
y changes back to the community, how should this flavor of the package be n=
amed? It seems less than ideal to have two very similar packages in the tre=
e; 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 &#39;dhcp&#39; i=
s defined. I&#39;m not sure how best to proceed in this case. I&#39;m also =
not fully convinced that changing the existing package is the right thing t=
o do; I suspect there are folks who don&#39;t want LDAP support.</div><div =
dir=3D"auto"><br></div><div dir=3D"auto">If there are examples among existi=
ng packages I could use as templates I&#39;m happy to replicate.</div><div =
dir=3D"auto"><br></div><div dir=3D"auto">Thanks!</div><div dir=3D"auto"><br=
></div></div>

--0000000000005d302c058379a849--


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---