This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: [libc-alpha] Re: Wish for 2002 ...
- From: Shawn Starr <spstarr at sh0n dot net>
- To: "Martin v. Loewis" <martin at v dot loewis dot de>
- Cc: kaz at ashi dot footprints dot net, <libc-alpha at sources dot redhat dot com>
- Date: Sun, 13 Jan 2002 19:27:59 -0500 (EST)
- Subject: Re: [libc-alpha] Re: Wish for 2002 ...
Fair enough, but I dont want to have to see say 100 libraries just for
each different C function thats worse then library hell.
libstrblowp.so
listrbleh.so
libnonstandardcfunctions.so
and so forth.
On Sun, 13 Jan 2002, Martin v. Loewis wrote:
> > I'm just arguing that if for example all the "other" *BSDs, unixes or
> > whatever have you decide to include say strblowup() and the GNU C library
> > doesn't. Won't that make us look like fools for not supporting
> > it. EVEN THOUGH it hasn't (yet) been adopted by the POSIX standards body?
>
> No. If people find that they cannot run the most recent FOOBAR
> application because strblowup is not supported, *that* may make us
> look like fools - atleast if enough people care about running FOOBAR.
>
> Of course, that won't happen: If FOOBAR is free software, somebody
> will contribute a patch to provide a portable strblowup to the FOOBAR
> maintainers, along with enough configuration magic to determine the
> system strblowup where available. In addition, other people will
> produce a libstrblowup.so.
>
> Notice how many GNU packages incorporate a complete gettext
> installation. Nobody sees it as a problem that many problems
> (including various BSDs) still do not provide a gettext implementation
> in the C library, even though it is in wide use.
>
> Regards,
> Martin
>
>