X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-3.4 required=5.0	tests=BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,TW_SV
X-Spam-Check-By: sourceware.org
Message-ID: <502D2391.2030000@acm.org>
Date: Thu, 16 Aug 2012 09:45:05 -0700
From: David Rothenberger <daveroth AT acm DOT org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Promote sqlite 3.7.13-1 from test status?
References: <announce DOT 5029275C DOT 4040009 AT etr-usa DOT com> <502C0B7D DOT 10909 AT etr-usa DOT com> <loom DOT 20120816T092134-266 AT post DOT gmane DOT org> <20120816085016 DOT GB5536 AT calimero DOT vinschen DOT de> <502CCBB1 DOT 2070600 AT etr-usa DOT com> <20120816105507 DOT GD17546 AT calimero DOT vinschen DOT de> <502CE120 DOT 4050900 AT etr-usa DOT com> <20120816122654 DOT GG17546 AT calimero DOT vinschen DOT de> <502D1967 DOT 7090705 AT etr-usa DOT com> <20120816160656 DOT M21257 AT ds DOT net>
In-Reply-To: <20120816160656.M21257@ds.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On 8/16/2012 9:34 AM, Brian Wilson wrote:
> Corina is correct, Cygwin is supposed to be a Posix compliant environment so 
> the SQLite package should follow the Posix standard as the default 
> behavior.  If you want to use Windoze tools, why are you using Cygwin?  If 
> you really must, why not set up Apache under Cygwin and access the Cygwin 
> Subversion repository through the defined http server interface and the 
> issue of file locking becomes moot.

The locking issue isn't only related to the repository, it's related to
the workspace itself. The problem people have is when they use
TortoiseSVN and Cygwin svn with the same workspace.

> If this solution isn't acceptable, Cygwin Subversion should use a
> different DB and drop SQLite.

As the current Subversion svn packager, I can say I'm not going to do
that. Subversion upstream only supports SQLite.

From a Subversion perspective, I think turning off the TortoiseSVN icon
cache is a reasonable work-around for those that must use both tools.
But as Warren pointed out, Subversion may not be the only case when a
Cygwin tool and a Windows tool want to access the same database at the
same time. I can understand the point that Cygwin SQLite should be
behave POSIX-ly, but if the locking is handled solely within SQLite
itself, does it really matter? Using the same locking that
Windows-native SQLite uses does seem to avoid some interaction issues
without causing any issues for Cygwin programs, so that's a net plus, right?

-- 
David Rothenberger  ----  daveroth AT acm DOT org

genius, n.:
        Person clever enough to be born in the right place at the right
        time of the right sex and to follow up this advantage by saying
        all the right things to all the right people.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple