On Sunday 19 January 2014 13:07:24 Robin H. Johnson wrote: > On Sun, Jan 19, 2014 at 05:52:48AM -0500, Mike Frysinger wrote: > > with glibc-2.17 in stable now and glibc-2.19 release in like ~2 weeks, > > glibc 2.18 is heading to ~arch. there's been very little reported > > breakage reported thus far ... i hope it's because there isn't any vs > > people aren't using it. so if people want to try it out ahead of time, > > that'd be nice. > > What ever happened with the rpc/libtirpc changes?
unfortunately libtirpc isn't feature complete with glibc. so upstream glibc
reverted the rpc removal and made it into a configure time flag which Gentoo
has
enabled (i.e. we ship rpc headers/linkable symbols). which is why the bug
onslaught died down.
this doesn't preclude anyone from switching their package today to libtirpc;
there are a good number of packages where the functionality it provides is
sufficient. in fact, you generally want to do that:
- you'll get IPv6 support (which glibc refuses to add)
- it'll make packages work on other C libraries (like uClibc)
- will let us stop enabling rpc functionality in glibc (we want)
- other extensions being added to libtirpc?
we still have the tracker open:
https://bugs.gentoo.org/381391
> Will packages that used RPC headers from glibc need more changes, and if
> so, what?
the idea was to make libtirpc have general feature parity with glibc. there's
very few people working on this upstream though (the few maintainers are
common NFS peeps so they tend to focus more on that). still, some
functionality is being added slowly.
-mike
signature.asc
Description: This is a digitally signed message part.
