[Libtirpc-devel] glibc/libtirpc and future of client RPC code
Ondřej Bílka
neleai@seznam.cz
Fri Jun 26 11:52:00 GMT 2015
On Thu, Jun 25, 2015 at 05:33:58PM +0200, Thorsten Kukuk wrote:
> On Thu, Jun 25, Chuck Lever wrote:
>
> > I like the second solution: move YP/NIS/NIS+ to one or more
> > separate upstream projects, and package them independently of
> > glibc and libtirpc.
>
> Yes, that's currently my prefered solution, too.
> libnss_nis and libnss_nisplus needs to be a drop in replacement,
> libnsl could have a higher version number and be installed
> in parallel.
> This would mean we would need a switch to disable building
> the nis directory in glibc, or at least to disable building
> and installing libnss_nis and libnss_nisplus and installing
> the libnsl header files.
>
> > What code in libtirpc calls on YP and NIS+ ? Should that be
> > moved as well?
>
That would be nice. As glibc libnns_nis are in maintainance mode if you
could make stable replacement we would welcome removing these and
telling distros to add dependency on your library for future version.
More information about the Libc-alpha
mailing list