introduction | devel | download | cvs | docs | mailing lists | resources

mirrors | freshmeat | sourceforge

---

To run rproxy, you will need to install matching versions of librsync and rproxy packages, in that order. (From 0.9.1, the package previously known as libhsync is now called librsync.

We use a Linux-style version numbering scheme, where 0.x.y is stable if x is even, and unstable if x is odd.

Prior to release 0.9.1, librsync was known as libhsync. We've decided to build just a single library, and so we're using the more-recognized name.

version	library [news]	rproxy
0.9.5	librsync-0.9.5.tar.gz	not yet
0.9.4	librsync-0.9.4.tar.gz	not yet
0.9.3	librsync-0.9.3.tar.gz	not yet
0.9.2	librsync-0.9.2.tar.gz	no corresponding rproxy release
0.9.1	librsync-0.9.1.tar.gz	no corresponding rproxy release
0.9.0	libhsync-0.9.0.tar.gz	no corresponding rproxy release
0.5.7	libhsync-0.5.7.tar.gz	rproxy-0.5.7.tar.gz

prerequisites

rproxy is developed and tested on Debian GNU/Linux (i86), but intended to be portable to other systems. There should be relatively little Unix-specific code.

To develop the code, you might need

• popt - command line processing library
• autoconf
• libtool
• automake
• Perl - 5.005 or so

At various times, librsync has been observed to run on

• i686-pc-gnu-linux (debian/2.2 and redhat/6.2)
• sparc64-unknown-gnu-linux (debian/2.2)
• solaris-2.6 and 2.8
• FreeBSD

The Alpha processor is currently broken in 0.9 because the library does unaligned memory access.

licensing

rproxy is licensed as two separate parts to aid adoption of the code as a standard.

The underlying library, librsync, is released under the terms of the GNU Lesser General Public License. The proxy code itself is released under the GNU General Public License.

Briefly, this means that the library may, subject to certain conditions, be integrated into free or nonfree application programs. Changes to the library itself, and the library source code must be contributed back to the community. You should consult the license texts for more details.

If you would like to add rproxy functions to your software but the LGPL is a problem then please contact us.

The rproxy protocol itself is unencumbered: anyone is free to write, use, and redistribute their own implementation. Again, please contact us to coordinate our development.