On 2012-02-03 10:39, jomifo wrote:
One thing that didn't work properly though was invoking subversion commands on the aliased files. It complains about the file not being in a working copy folder. I think TM2 should run the svn command on the source path, not the path of the alias.
It might be good to have some sort of option for that, but in general it's not workable. Subversion (and I assume Mercurial and Git) allows you to put symlinks themselves under version control. Maybe some heuristic like:
if file is symlink: if symlink is under version control: act on symlink else if target is under version control: act on target
Seems like it'd need a lot of special cases though, and possibly some sort of manual override as well. It's a messy work-around for something that used to be easy.
(Forgive me if there's something special about MacOS's aliases. AFAIK, aliases are just another mechanism to implement symlink functionality left over from the pre-OSX days.)