This is the mail archive of the
mailing list for the glibc project.
Re: Reverting removal of exporting sunrpc code for glibc 2.16?
- From: Aurelien Jarno <aurel32 at debian dot org>
- To: Andreas Jaeger <aj at suse dot com>
- Cc: libc-alpha at sourceware dot org, ldv at altlinux dot org, allan at archlinux dot org,debian-glibc at lists dot debian dot org, vapier at gentoo dot org,raj dot khem at gmail dot com, law at redhat dot com, matz at suse dot de,Adam Conrad <adconrad at debian dot org>
- Date: Wed, 9 May 2012 07:51:07 +0200
- Subject: Re: Reverting removal of exporting sunrpc code for glibc 2.16?
- References: <email@example.com>
On Tue, May 08, 2012 at 04:13:28PM +0200, Andreas Jaeger wrote:
> I'd like to have feedback - especially from the glibc distribution
> maintainers - whether we should revert the following change for glibc 2.16:
> * The RPC implementation in libc is obsoleted. Old programs keep working
> but new programs cannot be linked with the routines in libc anymore.
> Programs in need of RPC functionality must be linked against TI-RPC.
> The TI-RPC implementation is IPv6 enabled and there are other benefits.
> Visible changes of this change include (obviously) the inability to link
> programs using RPC functions without referencing the TI-RPC library and
> removal of the RPC headers from the glibc headers.
> Various distros - including Fedora and openSUSE - have been reverting this
> patch locally already. Looking at the libtirpc project, the TI-RPC library
> is not ready to be a full replacement and they need help to become a full
> replacement. Right now I see no progress from them - but once it's a
> replacement, I'm all for obsoleting the glibc code again.
> Packages can still choose to use libtirpc instead of sunrpc, they can be
> installed in parallel in a system,
I think it is the way to go.
Aurelien Jarno GPG: 1024D/F1BCDB73