The subversion sources include several useful tools (shell scripts, etc) that should get installed somewhere. I am attaching a simple patch to the dev-util/subversion ebuild to copy those tools into /usr/share/subversion. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 53199 [details, diff] Install the subversion tools into /usr/share/subversion
Some of the tools provided in tools/ already gets installed: - client-side,examples,hook-scripts are installed into /usr/share/doc/${PF}/tools (see client-side,examples, hook-scripts, line 224). - hot-backup.py is installed into /usr/bin/svn-hot-backup I don't use anything else out of tools (yet), but I guess this opens the discussion of what else to include...
(In reply to comment #2) > - client-side,examples,hook-scripts are installed into /usr/share/doc/${PF}/tools (see client-side,examples, > hook-scripts, line 224). Unfortunately, this prevents using a symlink or hard-coded path to reference those scripts across upgrades (since several of them are useful without modification). > - hot-backup.py is installed into /usr/bin/svn-hot-backup Hrm, didn't see that. That's good.
It is fixed in subversion-1.5_pre26086 in Eaedificāta Repository. http://www.ffta.host.sk/Eaedificata/index.html Installation of extra files is controlled by "extras" USE flag. These files are installed to constant location - "/usr/share/subversion".
*** Bug 135803 has been marked as a duplicate of this bug. ***
fixed in 1.4.4-r4