Re: Can't commit contents of symbolically linked files with Subversion 1.7.2...

Guten Tag Stefan Sperling,
am Dienstag, 24. April 2012 um 12:19 schrieben Sie:

> you mention that you're using 1.7.2.
> Have you tried 1.7.4?

I upgraded and there were no changes in my described behaviour.
Subversion seems to recognized the change of the file to a symbolic
link itself, which seemed to be ignored in earlier versions of my
client.

> Did you add the symlinks to version control?

No, each customer folder was a somewhen branched copy of the reference
folder and does have all of it's own versioned files and folders. The
links were just created on the filesystem level by deleting the
versioned file and replacing it with a ln -s to toe same file in the
reference folder. No svn operations involved, only filesystem and in
earlier versions of the svn client this was fully transparent.
Subversion didn't recognized changed file types, from native file to
symbolic link, but only saw changes in file contents itself, if the
referenced file got changed.

> It sounds like perhaps your case would be better handled by unversioned
> symlinks. Please experiment with versioned/unversioned symlinks in 1.7.4
> and check if you can get the desired behaviour.

I can't use versioned symlinks at all because the reference folder is
trunk, not present on the production folders, I have Windows clients
which needs the customer-specific files and where the symbolic links
won't work etc.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning       E-Mail:Thorsten.Schoening_at_AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
Telefon.............030-2 1001-310
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hanover HRB 207 694 - Geschäftsführer: Andreas Muchow