Comment 15 for bug 9860

At Sat, 06 Nov 2004 13:34:27 +0100,
Eric Valette wrote:
> > OK, we will ship /usr/include/nptl in future, like
> > /usr/lib/libpthread.a issue (#276062). I tagged this bug as wishlist,
> > and changed title, and merged with #276062. If you have another
> > comments, please let us know.
> >
> > Regards,
> > -- gotom
>
> I beg to disagree : it is a clear bug to compile with linuxthread
> includes when running NPTL threads. Not a whislist.
>
> Doing this you are behaving like a child saying everything I do is
> perfect. Come on, grow up... And by the way, the debian patched glibc
> does not seem to work with ntpl static...

Yes, I think you're correct. I didn't deny your opinion. So I tagged
it as wishlist for working future glibc package after sarge. It's not
"closing bug". I have tagged for glibc packages as long as I can,
because we have over 400 bugs - it's important to classify which bugs
are user-requested matter, and which bugs are actual glibc code fault.
We're effort to fix bugs (I closed over dozens of bugs in this year),
but everyday we're getting another bugs (and half of bugs are not
glibc related).

It's worthwhile including nptl things. If you want to include it,
it's nice to send your patches. Note that I'm feel so not pleasure,
because we're _not_ your subcontractor for your job.

> A whishlist would be please upgrade to glibc 2.3.3 because your libc is
> so old...

Eric, please calm down.

You need to educate the current status of glibc package. The current
status is "base-freeze". Even if we update it, release managers
decide to drop that package from sarge (and that decision is quite
correct). If you don't read debian-glibc lists, read and search my
opinion. I have been waiting to update glibc over _one year_. I'm
preparing glibc-snapshot package in experimental, so once it's
included in experimental, you can put your patch easily.

Regards,
-- gotom