Re: [rdiff-backup-users] librsync.so and _librsync.so

[Joe Steele]

My understanding is that librsync is only needed for building 
rdiff-backup (more specifically, for building _librsync.so). 
During the build, rdiff-backup/_librsync.so is created and is 
statically linked against librsync.a.

Once rdiff-backup is built, librsync can be uninstalled and 
rdiff-backup should continue to function normally (because it was 
statically linked).

--Joe

On 12/15/2010 9:16 AM, Dominic Raferd wrote:
> Can anyone explain the relationship between /usr/lib/librsync.so,
> and /usr/local/lib/python2.6/dist-packages/rdiff_backup/_librsync.so?
>
> They are not the same:
>
>     * /usr/lib/librsync.so is symlinked to
>       /usr/lib/librsync.so.1.0.2 which is 46612 bytes, and I
>       think came via apt-get install librsync-dev
>     * /usr/local/lib/python2.6/dist-packages/rdiff_backup/_librsync.so
>       is 30110 bytes, is located in my rdiff-backup installation
>       location, and seems to have come with rdiff-backup in the
>       tarfile
>
> Both Rdiff.py and robust.py import librsync [i.e. librsync.py?],
> and librsync.py imports _librsync.
>
> When I built rdiff-backup I specified --librsync-dir=/usr/lib.
>
> Which file is rdiff-backup using: librsync.so or _librsync.so?
> Are they alternatives and if so which one should it use?
>
> Dominic