Home/ Questions/Q 522299
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T08:20:22+00:00

We use svn:externals to specific revisions of a library, e.g. like xyzlib -r12345 https://asdf.asdf.local/xyzlib/trunk/

  • 0

We use svn:externals to specific revisions of a library, e.g. like

xyzlib -r12345 https://asdf.asdf.local/xyzlib/trunk/

When you make a modification in your working copy to such a checked out external, it is possible to commit even though the external links to a specific revision and not the HEAD.

When you run svn update after the commit, the changes will be gone in the working copy because subversion reverts everything back to the revision 12345. So you never really see the changes yourself but they still are in the HEAD, which is bad.

Is it possible to forbid commits only when the external does not point to the HEAD revision?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    For these kinds of validations I would also recommend a pre-commit hook, but instead of writing a script which can easily turn out to be impossible to understand I recommend using a library like SVNKit – http://svnkit.com/ (if you know Java).

    I’ve written a few pre-commit hooks myself using this library and it is quite easy to work with. You write a small runnable Java program which is called from the pre-commit hook by Subversion. Then it is easy to extract e.g. properties or parts of the URL to do the validation and reject the commit if it doesn’t apply to your “rules”.

    Take a look at the SVNLookClient and SVNChangeEntry classes – they have methods for the most common cases (e.g. extracting info about a commit in progress.)

    • 0