> Some more notes on version numbers:
> 
> 	- major version numbers need not be bumped unless you change an
> 	  *existing* interface to the library in an incompatible way (eg.
> 	  the recent change to _ctype_).

this also includes:

	'public' (i.e. not library internal) functions which have new
		arguments added.
	changes to headers so that flags passed in as args to function change
	changes to headers in which structures which are manipulated
		by the libraries have their sizes changed
	etc.

is that correct?  if so, the 'major' version of libc is prolly going
to have to be bumped for most new releases of the DB stuff, and also
almost always whenever libc stuff is updated from uunet...

given that, keeping libraries at 0.* until the next release could
be tough.  (for the curses library, it will be impossible.)

thoughts?


chris
	

------------------------------------------------------------------------------