[foo-cvs] foo/libfoo configure.ac,1.6,1.7

[Martin R. <ru...@us...>]

Update of /cvsroot/foo/foo/libfoo
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv12225

Modified Files:
	configure.ac 
Log Message:
changed release and versioning information

Index: configure.ac
===================================================================
RCS file: /cvsroot/foo/foo/libfoo/configure.ac,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** configure.ac	2 Aug 2004 00:30:06 -0000	1.6
--- configure.ac	2 Aug 2004 02:20:58 -0000	1.7
***************
*** 6,10 ****
  # $Id$
  
! AC_INIT(libfoo,0.1.0,foo...@li...)
  
  AC_PREREQ(2.53)
--- 6,10 ----
  # $Id$
  
! AC_INIT(libfoo,0.1.0pre1,foo...@li...)
  
  AC_PREREQ(2.53)
***************
*** 15,19 ****
  AM_CONFIG_HEADER(src/config.h)
  
! SHARED_VERSION_INFO="0:1:0"
  
  AC_CHECK_PROG(autogen, autogen, yes, no)
--- 15,47 ----
  AM_CONFIG_HEADER(src/config.h)
  
! dnl Here are a set of rules to help you update your library version
! dnl information:
! 
! dnl   1. Start with version information of `0:0:0' for each libtool library.
! 
! dnl   2. Update the version information only immediately before a public
! dnl      release of your software.  More frequent updates are unnecessary,
! dnl      and only guarantee that the current interface number gets larger
! dnl      faster.
! 
! dnl   3. If the library source code has changed at all since the last
! dnl      update, then increment REVISION (`C:R:A' becomes `C:r+1:A').
! 
! dnl   4. If any interfaces have been added, removed, or changed since the
! dnl      last update, increment CURRENT, and set REVISION to 0.
! 
! dnl   5. If any interfaces have been added since the last public release,
! dnl      then increment AGE.
! 
! dnl   6. If any interfaces have been removed since the last public release,
! dnl      then set AGE to 0.
! 
! dnl    *_Never_* try to set the interface numbers so that they correspond
! dnl to the release number of your package.  This is an abuse that only
! dnl fosters misunderstanding of the purpose of library versions.  Instead,
! dnl use the `-release' flag (Note: Release numbers), but be warned that
! dnl every release of your package will not be binary compatible with any
! dnl other release.
! SHARED_VERSION_INFO="0:0:0"
  
  AC_CHECK_PROG(autogen, autogen, yes, no)