From owner-cvs-gnu  Mon May  8 23:05:11 1995
Return-Path: cvs-gnu-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id XAA04564
          for cvs-gnu-outgoing; Mon, 8 May 1995 23:05:11 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA04543
          ; Mon, 8 May 1995 23:04:20 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id QAA29655; Tue, 9 May 1995 16:00:53 +1000
Date: Tue, 9 May 1995 16:00:53 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199505090600.QAA29655@godzilla.zeta.org.au>
To: ache@freefall.cdrom.com, asami@cs.berkeley.edu
Subject: Re: cvs commit: src/gnu/lib/libreadline Makefile
Cc: CVS-commiters@freefall.cdrom.com, cvs-gnu@freefall.cdrom.com,
        thud-users@freebsd.org
Sender: cvs-gnu-owner@freebsd.org
Precedence: bulk

> *   Modified:    gnu/lib/libreadline  Makefile
> *   Log:
> *   Bump major number

>Aiyeeeeeeeeee!!!  Now I need to go into ports and recompile everything
>that requires this library.  Please, next time bump the version number
>when you change something, not right before the release when someone
>reminds you about it, okay?

>Also, to everybody on the cvs list -- if you are going to change a
>library version number between now and the release, please do it RIGHT
>NOW.  I'm going to run a "make world" on thud tonight and then rebuild

I still have libg++ and libforms on my list of things to change (I think
libncurses was done yesterday).

Should we bump the version number _every_ time the interface is changed
or extended?  This would be easiest to remember to do, but would result
in many more minor version numbers and recompiling.  Bumping the major
number is more important.  It's not clear how 2.0 packages work with
the current libg++ (gnuregexp was removed).

Bruce