On Nov 26, 2010, at 01:58, Ewgenij Sokolovski wrote:
>> 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.
>
> I lo
OK, thanks for the information. I think, the most reasonable solution for
me would be a bash script, which just copies the file to be versioned
to my working copy at regular intervals. That should be easy...
> I believe he's thinking of "svnput" whose source is here:
>
> http://svn.apache.org/rep
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
> The short answer is "no".
Any way hardlinks/symlinks could help?
E.g. symlinking an out-of-working-copy-file to a working-copy-file?
>I hope I guessed right what you meant.
Yes, you did :)
> 1. You create a solution on top of SVN.
> This means e.g. writing a batchfile that creates or syncs a WC with the
> according configuration file. You might also be able to employ symlinks or
> other features of your filesystem to your
Note up front: You are mixing up the terms "repository" and "working copy" in
your message, I hope I guessed right what you meant.
On Thursday 25 November 2010, Ewgenij Sokolovski wrote:
> I have the following issue. I would like to version a configuration file,
> which resides outside of my svn-
