librsync  2.3.1
versioning.md
1 # Versioning {#versioning}
2 
3 librsync uses the [SemVer] approach to versioning: the major version number
4 changes when the API changes in an incompatible way, the minor version
5 changes when new features are added, and the patchlevel changes when there
6 are improvements or fixes that do not change the API.
7 
8 [SemVer]: http://semver.org/
9 
10 The solib/dylib version is simply the major number of the library version.
11 
12 The librsync signature and patch files are separately versioned under
13 application control, by passing a ::rs_magic_number when creating a job.
14 
15 The library version can be checked at runtime in ::rs_librsync_version.
16 
17 See [NEWS.md](NEWS.md) for a list of changes.
18 
19 \note Only the public interface, defined in \ref librsync.h, is covered
20 by the API stability contract. Internal symbols and functions may change
21 without notice.
rs_magic_number
A uint32 magic number, emitted in bigendian/network order at the start of librsync files...
Definition: librsync.h:65
LIBRSYNC_EXPORT char const rs_librsync_version[]
Library version string.
Definition: version.c:25