diff options
| author | enge <enge@211d60ee-9f03-0410-a15a-8952a2c7a4e4> | 2008-09-16 14:05:18 +0000 |
|---|---|---|
| committer | enge <enge@211d60ee-9f03-0410-a15a-8952a2c7a4e4> | 2008-09-16 14:05:18 +0000 |
| commit | 47c26e9818725f9a50c61ebfd490a566ad399d7b (patch) | |
| tree | 836321cc7716a7262ee799e0077b6857a1911f3d /README.dev | |
| parent | a319cf96b86df7d7411395e89ee572dcfd11a26a (diff) | |
| download | mpc-47c26e9818725f9a50c61ebfd490a566ad399d7b.tar.gz | |
minor changes prior to the 0.5 release
git-svn-id: svn://scm.gforge.inria.fr/svn/mpc/trunk@170 211d60ee-9f03-0410-a15a-8952a2c7a4e4
Diffstat (limited to 'README.dev')
| -rw-r--r-- | README.dev | 23 |
1 files changed, 14 insertions, 9 deletions
@@ -1,14 +1,19 @@ -Source code from Subversion repository: -To compile source code obtained from Subversion repository, you need autoconf, -automake and libtools packages. To create the configure file, type: +Source code from the subversion repository +------------------------------------------ +To compile source code obtained from the subversion repository, +make sure you have installed the autoconf, automake and libtools packages. +Execute $ autoreconf -i -To make a new release: +Creating a new release +---------------------- - 1) create a tag for the new release, for example: - - $ svn cp svn+ssh://zimmerma@scm.gforge.inria.fr/svn/mpc/trunk \ - svn+ssh://zimmerma@scm.gforge.inria.fr/svn/mpc/tags/0.4.6 - +1) Update the version number in configure.ac ("AC_INIT (mpc, _version_...)") + and in INSTALL. +2) Check that NEWS, BUGS and TODO are up to date. +3) Execute "autoreconf; touch doc/mpc.texi; make dist". + This updates the date and version number in doc/version.texi and + creates the tarball for distribution. +4) Commit the changes to svn. |