> -----Original Message-----
> From: Mark Phippard [mailto:markphip_at_gmail.com]
> Sent: woensdag 18 februari 2009 17:08
> To: Bert Huijben
> Cc: Ivan Zhakov; Paul Burba; dev_at_subversion.tigris.org
> Subject: Re: Attn: Windows Devs -- Need to add missing sqlite build
> for Windows (issue #3364)
> On Wed, Feb 18, 2009 at 11:02 AM, Bert Huijben <rhuijben_at_sharpsvn.net>
> > Is it a problem to just keep the current build option?
> > (+1 on making the amalgamation default on Windows)
> > The amalgamation build makes it impossible to re-use Sqlite from
> > applications that use both Subversion and Sqlite (Requiring them to link
> > two separate copies).
> Do we really want to support that? I'd assume for example, we do not
> want application to use SQLite to directly access whatever database we
> are using. So the only issue would be a client that uses Subversion
> and also uses SQLite for its own datastore. In that scenario,
> assuming it exists, is it so bad for the application to use another
> SQLite for that purpose?
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
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
Using sqlite shared works right now... Why disable it?
Why break specific Windows scenarios on purpose?
Just for the fun of doing this because windows is .... (fill in your
favorite problem) ?
Received on 2009-02-18 17:46:21 CET