On Tue, Apr 24, 2012 at 05:38:20PM +0200, Thorsten Schöning wrote:
> 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.
Ah, so you are obstructing a versioned file with a symlink?
That's why 'svn status' shows the '~' symbol which means "obstructed".
It seems that the smarter handling of symlinks in 1.7 is what
breaks your current workflow. I don't think Subversion ever
intentionally ignored the fact that you are replacing a versioned
file with an unversioned symlink. I think you should somehow rearrange
your project so you don't have to do that. Perhaps you can move the
versioned file to a different location?
> 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.
Maybe externals will help?
Received on 2012-04-24 17:49:28 CEST