4 This document describes a few basic tasks for managing the codebase;
5 see http://wiki.zmanda.com/ for more detailed developer-oriented
11 Edit the clearly marked section in gnulib/regenerate/regenerate,
12 then re-run that script as directed below.
17 This should probably be done after most releases, so that we have
18 adequate time to uncover any bugs or problems in the new gnulib before
19 we make another release.
21 To update the gnulib files included with Amanda, you'll first need a git
22 working copy of gnulib; let's call it $GNULIB_BR:
25 git clone git://git.savannah.gnu.org/gnulib.git
28 See http://www.gnu.org/software/gnulib/ for more information. Then, in the
29 root of the Amanda source, run
31 GNULIB_TOOL=$GNULIB_BR/gnulib-tool ./gnulib/regenerate/regenerate
33 Use 'svn status' to figure out what changed, and 'svn add' / 'svn rm'
34 to inform Subversion. Then re-run autogen, configure, make, and test
37 Get the object ID of the latest commit, using 'git show', and replace the
38 previous object ID in Amanda's gnulib/regenerate/regenerate, so that other
39 developers can access the same "release" of gnulib as you did.
44 Libtool includes such useful files as config/config.guess.
45 Occasionally (probably right after a release), these files should be
46 updated. On a machine with libtool installed, simply run
47 libtoolize --force --copy
49 Then use 'svn status' to see what changed, test it out, and commit.
54 The gettext library contains a significant number of files. Assuming
55 you have the proper version of gettext installed, these files can be
60 and then adjusting as appropriate with 'svn add' / 'svn rm', testing,
61 and committing. Note that this script post-processes the results of
62 autopoint rather extensively, and will probably need to be adjusted
63 for a new version of autopoint.