[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: subversion link capability

From: Grégoire Welraeds <gregoire.welraeds_at_side-international.com>
Date: 2005-09-09 10:06:32 CEST

Janulewicz, Matthew wrote:

> It’s been a while since I worked with Source Safe, but my philosophy
> on changing tools is that you always do it for a reason. If you import
> bad habits from the old tool, then you’re setting yourself up to make
> the same mistakes. Except faster. ;)
> Tool changes are always a good time to refactor code. As a CM guy,
> I’ve had to do some ‘human engineering’ in my past to get managers to
> ‘encourage’ their folks to adhere to coding standards, sane project
> tree layout, etc. Not sure what kind of influence you have, but in my
> opinion, it’s a bad sign when you have to have the same file in two
> places in source control. Your engineers are just begging for
> divergance. A better practice (although still hacky) is to have your
> build scripts copy/stage the files where they need to be, but one
> tenet of SCM is ‘one source’. It’s still sloppy code layout/design.
I completly agree with you. I'll do my best to advocate a better
layout/design of our code. But I'm not the decision maker and we have
some tight deadlines. Anyway, we already planed a meeting with the
engineers to address this problem. I'll tell them what I really think
about their coding habits... :-)

> That being said, Subversion does support checking in symlinks, but as
> you said they only work on Unix. This may be a longshot, but at the
> last place I worked we used Perforce and I checked in a Windows
> shortcut (the actual .lnk file) for a directory and it seemed to do
> what I wanted it to do. You couldn’t ‘browse’ the shared directory in
> the tool, but when you synced your code, it would pull both trees. You
> might want to give that a try.
Windows shortcut are an unacceptable solution, really. The reason is
that shortcut are based on absolute path. As soon as you move both the
shortcut and the target to another place, the link will not work
anymore. As such, It would require all the developpers to have the WC at
exactly the same place (eg: c:\projects\...). And the shortcut would
stop to work as soon as the files are set on a CD for distribution...


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 9 10:08:49 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.