Libc6

[Will Lowe <harpo@udel.edu>]

In porting clisp to libc6,  I've discovered that the entire
/usr/include/ hierarchy has been completely rearranged.  Two questions:

a) is this rearrangement described anyplace?  I understand that in general
we're supposed,  from now on,  to avoid #include-ing <linux/*.h> and
instead go for <sys/*.h>,  which often means using stuff that's actually
defined in <gnu/*.h> ... it's probably obvious to you now that I'm real
confused.

b) Since Gnu Libc 2 (our libc6) is still not out of beta,  will these
things be changing AGAIN soon?  (Read:  Should I wait until we get to
using the stable libc6 version?)

					Thanks.

                     					Will

			        harpo@udel.edu
			       lowe@cis.udel.edu
			http://www.cis.udel.edu/~lowe/
*****************************************************************************
Good Idea: 	Feeding Stray Cats in the Park.
Bad Idea:	Feeding Stray Cats in the park ... to a bear.
***************************************************************************** 


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .