summaryrefslogtreecommitdiff
path: root/librsync/README.CVS
blob: e7e9847c7e75683b0c1957da1ec1a54e6f2d7ed6 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
If you're building from CVS, things are slightly more complicated than
usual.  I hope these instructions will tell you all you need to know.
Please mail <mbp@samba.org> if they are unclear or incorrect.


>> Requirements

To build from CVS you'll need automake, autoconf, and libtool, plus a
compiler, make and so on.  On Debian, you can simply say

  # apt-get install automake autoconf libtool

To generate API documentation, you will need Doxygen, Latex and
GhostView:

  # apt-get install doxygen gs tetex

>> Downloading

  $ cvs -d:pserver:cvs@pserver.samba.org:/cvsroot login 
  [ enter "cvs" ]
  $ cvs -z3 -d:pserver:cvs@pserver.samba.org:/cvsroot \
    -d YOUR_DIRECTORY co librsync

You can choose the name of the directory that will hold the source
here.  If you have no opinion, just omit the `-d YOUR_DIRECTORY' and
it will go into `librsync'.

For more details, see the web site.


>> Building

  $ cd YOUR_DIRECTORY
  $ ./autogen.sh [OPTIONS]
  $ make all check

You can pass all the ./configure options to autogen, including --help.


>> Debugging

If you are using GNU libc, you might like to use

  MALLOC_CHECK_=2 ./rdiff

to detect some allocation bugs.


>> Sending patches

If you make a change to the source and would like to contribute it
back, do this:

  $ cvs diff -u -N >/tmp/my.librsync.patch

and mail it to the list.


Id: README.CVS,v 1.11 2001/03/07 08:11:27 mbp Exp