Date: Mon, 8 May 1995 23:41:09 -0700 From: asami@cs.berkeley.edu (Satoshi Asami | =?ISO-2022-JP?B?GyRCQHUbKEI=?= =?ISO-2022-JP?B?GyRCOCsbKEIgGyRCOC0bKEI=?=) To: bde@zeta.org.au Cc: ache@freefall.cdrom.com, CVS-commiters@freefall.cdrom.com, cvs-gnu@freefall.cdrom.com, thud-users@freebsd.org Subject: Re: cvs commit: src/gnu/lib/libreadline Makefile Message-ID: <199505090641.XAA27688@silvia.HIP.Berkeley.EDU> In-Reply-To: <199505090600.QAA29655@godzilla.zeta.org.au> (message from Bruce Evans on Tue, 9 May 1995 16:00:53 %2B1000)
next in thread | previous in thread | raw e-mail | index | archive | help
* I still have libg++ and libforms on my list of things to change (I think * libncurses was done yesterday). I already saw commit messages for libg++ and libncurses' version number changes. libforms doesn't seem to be used for any of the ports so it doesn't really matter to me when you fix it. * 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). I think we should change the number the first time the interface is changed after a release, and keep it that way until the next release. (No I don't think we should change the number EVERY time something is changed, some incompatibilities among -currents are inevitable anyway.) Then the person changing something that requires a version bump can just look at the commit logs to determine what to do. Satoshi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505090641.XAA27688>