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
22 CVS checkout of gnulib; let's call it $GNULIB_CO. Then, in the root
23 of the Amanda source, run
25 GNULIB_TOOL=$GNULIB_CO/gnulib-tool ./gnulib/regenerate/regenerate
27 Use 'svn status' to figure out what changed, and 'svn add' / 'svn rm'
28 to inform Subversion. Then re-run autogen, configure, make, and test
29 the result. If all is well, commit.
34 Libtool includes such useful files as config/config.guess.
35 Occasionally (probably right after a release), these files should be
36 updated. On a machine with libtool installed, simply run
37 libtoolize --force --copy
39 Then use 'svn status' to see what changed, test it out, and commit.
44 The gettext library contains a significant number of files. Assuming
45 you have the proper version of gettext installed, these files can be
50 and then adjusting as appropriate with 'svn add' / 'svn rm', testing,
51 and committing. Note that this script post-processes the results of
52 autopoint rather extensively, and will probably need to be adjusted
53 for a new version of autopoint.