On 12/12/2011 08:15 PM, Toshio Kuratomi wrote:
> To me, the easiest solution for you is probably going to be dropping ypserv
> from the distribution. But if that's not possible, then attempting to
> convince the gdbm upstream to switch back to GPLv2+ would likely be
> a worthwhile investment.
One thing worth looking into would be to build ypserv with qdbm which
according to the License tag is LGPLv2+.
See attached patch -- it is just for demonstration purposes
(ugly/fragile) but it does build successfully in my Rawhide mock. I
haven't tested it beyond building at all, I don't even use ypserv. If
it works, perhaps ypserv upstream would be interested in properly
integrating support for qdbm as a third alternative to gdbm and ndbm.
Possible upgrade caveat from qdbm-devel's hovel(3) man page:
"Hovel cannot handle database files made by the original GDBM."
diff --git a/ypserv.spec b/ypserv.spec
index 5770032..79e7fc8 100644
--- a/ypserv.spec
+++ b/ypserv.spec
@@ -33,7 +33,7 @@ Patch12: ypserv-2.26-shadow.patch
Patch13: ypserv-2.26-errmsg.patch
Patch14: ypserv-2.26-emptydomain.patch
Patch15: ypserv-2.26-retval.patch
-BuildRequires: gdbm-devel
+BuildRequires: qdbm-devel
BuildRequires: systemd-units
%description
@@ -70,6 +70,8 @@ machines.
%patch13 -p1 -b .errmsg
%patch14 -p1 -b .emptydomain
%patch15 -p1 -b .retval
+sed -i -e 's/<gdbm\.h>/<hovel.h>/' */*.[ch]
+sed -i -e 's/-lgdbm/-lqdbm/' configure
%build
cp etc/README etc/README.etc
@@ -78,6 +80,7 @@ export CFLAGS="$RPM_OPT_FLAGS -fPIC"
%else
export CFLAGS="$RPM_OPT_FLAGS -fpic"
%endif
+export CPPFLAGS="$( pkg-config --cflags qdbm )"
%configure --enable-checkroot --enable-fqdn --libexecdir=%{_libdir}/yp
make
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
