Mark Phippard wrote:
> On Wed, Feb 18, 2009 at 12:09 PM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
>>> No we don't want users to look in our database, but why can't I access my
>>> own sqlite database? (TortoiseSVN uses sqlite for its log cache if I
>>> remember correctly)
>> Ahem: no. The log cache uses its own binary format. No db backend at all.
>>> And why don't we want users to share the same sqlite installation on
>>> Windows, while we can't even specify a standard version of sqlite on other
>> shared libs on Windows is always a very bad idea. Only optimists who
>> never had their app in use by more than 2 people would even consider
>> such a thing.
>> Seriously: in TSVN, we use our own build script not just because we can
>> automate the whole build that way, but also to 'rename' all the shared
>> libs to avoid any possible problems of the so called 'dll hell'.
> This is what I was thinking too. Look how often we have to deal with
> crappy apps that dump old OpenSSL DLL's into the Windows\System32
> folder. I am also thinking of apps like TortoiseSVN and AnkhSVN that
> will use the latest Visual Studio to compile everything, and Subclipse
> and the command line which still use MSVC 6. We would not want those
> DLL's to mix.
Exactly. Windows is a hostile environment for applications.
That's why TSVN doesn't use any shared lib at all (except the
C-runtimes, but those are stored in the GAC and versioned even if they
use the same dll name). Even OpenSSL is linked statically in TSVN
(because of some stupid firewalls (which shall kept unnamed) putting
their completely outdated and non-standard configured dll in the
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2009-02-18 18:39:09 CET