> 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...
> 
Right. All these cases would make a new major version number necessary.
Any change in the *existing* interface visible to the outside world
mandates it.

> given that, keeping libraries at 0.* until the next release could
> be tough.  (for the curses library, it will be impossible.)
> 
> thoughts?
> 
I was just expressing my worry about gratuitous version bumping whenever
the odd "fixed missing semi-colon" would be committed, that's all.

-pk

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