On 03.09.2010 15:21, Loritsch, Berin wrote:
> Ok, so I'm directing at the wrong people. My apologies. Regarding
> the confidentiality notice: my company's mail server attaches it to
> all outgoing messages. There is nothing I can do about it. It
> wasn't there when I sent the original message.
> Keeping the SVN clients in sync is far more difficult than it should
> be. That is something you can't stick your head in the ground and
> ignore. Perhaps if I have already installed the core SVN software
> Tortoise could use the instance I've already installed? That would
> let me have my cake and eat it too.
> I am not the only one who has to work on a closed network, and the
> unfortunate truth of the matter is that getting synchronized version
> of SVN clients can be difficult when you have to have upgrades
> approved. It's a frustrating fact of life for a large number of
> people. Maybe not the majority, but it's been a fact of my
> development career.
> And yes, it is an insidious feature. It's a feature of subversion,
> but it is insidious to not be backwards compatible. It causes people
> to rant like this. The problem is everyone has their own copy of the
> subversion client, and can't possibly use an existing one. Windows
> rocks with this DLL hell.
You contradict yourself. First you say that TSVN should use the already
installed svn binaries, then you complain about the dll hell.
That's an oxymoron - you can't have one without the other. And that's
why TSVN will never, ever use anything that's not shipped with TSVN but
installed on your system (apart from system dlls).
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-09-03 15:24:15 CEST