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

Guten Tag Stefan Sperling,
am Dienstag, 24. April 2012 um 17:48 schrieben Sie:

> Ah, so you are obstructing a versioned file with a symlink?

Yes.

> That's why 'svn status' shows the '~' symbol which means "obstructed".

Thanks.

> 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 don't think so, I need the tag to be as it is now, because that's
what get's deployed to the production servers and it really consists
all a web application for a customer needs and I want it versioned in
one combined folder. Because former versions of the svn client seemed
to ignore my file replacement to a symlink we were able to implement
this fast bugfix process: Test the customer templates and most of the
configuration with the symlinked programs from trunk, fix the bug in
trink while testing it with the customer installation and if it was
fixed just commit on the development server once for trunk and once
for the customer folder. Only th latter brekas now so it seems I just
have to adjust my workflow to merge the commits from trunk to the
customer in a separate step and folder without the symlinks.

> Maybe externals will help?

Wouldn't know how, as I want the tags unchanged, and only wnated to
replace the binaries of the web application for the fast bugfix way
with the contents of the trunk, keeping all themes etc. of the
customer. Symlinks on filesystem level were a good way to trick
Subversion and achieve this.

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