repository·trunk·Indexed 20 days ago
https://github.com/apache/subversionDocumentation for Apache Subversion, including details on the utf8proc C library for Unicode normalization and encoding, the JavaHL high-level Java API, and SWIG-based Python and Ruby bindings for interacting with Subversion client operations and repository management.
Subversion 1.15 supports two distinct working copy formats:
| Feature | 1.8-compatible (Format 31) | 1.15-compatible (Format 32) |
|---|---|---|
| Default | Yes (default for SVN 1.15) | No |
| i525pod Support | No | Yes |
| WC State | Never "bare" | Becomes "bare" immediately |
| Compatibility | Accessible by SVN 1.8+ | Accessible only by SVN 1.15+ |
| Reversibility | N/A | Cannot be converted back to 1.8 |
The i525pod feature significantly reduces the disk footprint of a Working Copy.
| Feature State | Typical Disk Usage |
|---|---|
| Standard (No i525pod) | ~2x the size of working files (contains a pristine copy of every unique file) |
| With i525pod | Slightly greater than the size of working files (only stores pristines for modified files) |
svn commit will remove the pristines for the files being committed.The i525pod feature (implemented in Subversion 1.15) optimizes disk space usage by only storing pristine copies (text bases) for files that are currently in a locally modified state.
When i525pod is enabled, certain operations that were previously offline now require repository contact to "hydrate" necessary pristine copies. This may require authentication and can introduce a delay before the command begins its primary task.
svn cat (base version)svn diff (base against working)svn resolve (including conflict resolution in merge or update)svn revertsvn diff (comparing repository to WC)svn mergesvn resolvesvn switchsvn updatesvn checkout --forceFetching text bases ... with dots representing files fetched. However, svn diff and svn cat do not provide progress feedback and may appear to hang while hydrating.To use svnpubsub, you must first deploy the service to your server.
svnpubsub directory to /usr/local/svnpubsub (or /opt/svnpubsub on Debian systems).rc.d/ directory. Add these scripts to your operating system's boot process (e.g., using rc.conf(5) or update-rc.d(8) depending on your OS).The i525pod feature is an optional component of Subversion 1.15. It is enabled on a per-Working Copy basis by upgrading the WC to the 1.15-compatible format.
Warning: Once a Working Copy is upgraded to the 1.15 format, it is no longer compatible with older Subversion clients (1.8 through 1.14) and cannot be downgraded.
To enable the feature, use either a fresh checkout or upgrade an existing WC using the --compatible-version=1.15 flag.
# For a new checkout
svn checkout --compatible-version=1.15 <URL>
# For an existing working copy
svn upgrade --compatible-version=1.15You can build the utf8proc C library using make or cmake.
make to compile the library.make install to install the library and header files. By default, these are installed to /usr/local/lib and /usr/local/bin. You can specify a custom directory using make prefix=/some/dir.make check to execute tests.make clean to remove generated files.To build using CMake, create a build directory and run the following:
mkdir build
cmake -S . -B build
cmake --build buildTo use the i525pod feature, the working copy (WC) must use the 1.15-compatible format (WC format 32). This format is required for i525pod functionality and results in a "bare" working copy.
Important constraints for 1.15-compatible format:
You can either create a new working copy in this format or upgrade an existing one.
# To check out a new working copy in 1.15-compatible format
svn checkout --compatible-version=1.15
# To upgrade an existing working copy to 1.15-compatible format
svn upgrade --compatible-version=1.15The library provides a CMake Config-file package. To use utf8proc in your own CMake-based project, use find_package and link against the utf8proc::utf8proc target.
add_executable (app app.c)
find_package (utf8proc 2.9.0 REQUIRED)
target_link_libraries (app PRIVATE utf8proc::utf8proc)To broadcast repository changes via svnpubsub, you must trigger the commit-hook.py script from your Subversion repository's post-commit hook.
Pass the repository path and the revision number as arguments:
commit-hook.py $REPOS $REV
Note: Since version 1.7, commit-hook.py accepts the same ordered arguments as the standard post-commit hook. If you do not require any other hooks to run in the server process, you can simply symlink commit-hook.py as your hooks/post-commit script.
commit-hook.py $REPOS $REVThe svn upgrade command is used to transition working copies between compatibility formats.
svn upgrade (or svn upgrade --compatible-version=1.8) upgrades a working copy to the 1.8-compatible format. This is useful for upgrading WCs from version 1.7 or older so that Subversion 1.8+ clients can use them.# Upgrade to 1.8-compatible format (default)
svn upgrade
# Upgrade to 1.15-compatible format (required for i525pod)
svn upgrade --compatible-version=1.15JavaHL is a high-level Java API for Subversion that provides a mostly native implementation using JNI (Java Native Interface). It is designed for developers implementing GUI clients or IDE plug-ins for Subversion.
Key characteristics:
libsvnjavahl-1.so on Unix, libsvnjavahl-1.dll on Win32) and a platform-independent Java bytecode archive (svn-javahl.jar).