On Nov 25, 2010, at 07:49, Ewgenij Sokolovski wrote:
>> 2. You turn the directory where the file is stored a working copy.
>> You can do so by simply creating a target dir in the repository
>> ("svn mkdir $URL/config") and checking out that dir in the
>> directory where the file is stored ("svn co $URL/config .").
>> You can then add the configuration file and commit, just like
>> with any other WC.
>
> Hmm, that would imply going to this configuration directory each
> time I want to commit, right? What I am searching for is a solution
> where I commit one single time in the working copy of my project and
> do not care about the rest.
I don't think you'll find that feature in Subversion. Though, again, you could
write a script, and instead of directly calling "svn commit", you would call
your script, which would "svn commit" in your working copy and again in the
system configuration directory. If there are changes in both places this would
result in two revisions with two log messages, of course, and the commits would
not be atomic.
>> I believe there also was a script or so to upload a single file to a
>> repository, which might be a third alternative.
>
> That's interesting. Do you know anything about this script?
I believe he's thinking of "svnput" whose source is here:
http://svn.apache.org/repos/asf/subversion/trunk/tools/examples/svnput.c
Or you could probably write something equivalent using any of the language
bindings.
