X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-3.2 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Message-ID: <502DBB67.7080405@acm.org> Date: Thu, 16 Aug 2012 20:32:55 -0700 From: David Rothenberger 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: <502C0B7D DOT 10909 AT etr-usa DOT com> <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> <502D3A5C DOT 7010500 AT etr-usa DOT com> <00ad01cd7bf6$7cc68a50$76539ef0$@motionview3d.com> <1345169297 DOT 10004 DOT 10 DOT camel AT YAAKOV04> In-Reply-To: <1345169297.10004.10.camel@YAAKOV04> 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: List-Subscribe: List-Archive: List-Post: List-Help: , 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 7:08 PM, Yaakov (Cygwin/X) wrote: > So you're saying that it is more important for Cygwin's sqlite3 to work > with a Windows program than it is for it to work properly with other > Cygwin libraries and programs? That doesn't sound very pragmatic to me. > Software built for Cygwin should _always_ follow *NIX behaviour. While I agree with your general point, Yaakov, I don't understand how the Windows-ish SQLite package does not work properly with other Cygwin libraries and programs. I suppose if another program tried to get a POSIXy lock on the SQLite database things would go wrong, but does that really happen in real life? Can anyone point to an example of the Windows-ish SQLite package causing a problem in Cygwin, other than Achim's one report? If SQLite using Windows locking doesn't break Cygwin programs in real life, but does break Windows programs that people use in real life (and not dumb people -- just people that really need/want to use Cygwin and Windows programs together on the same SQLite database), then is there really a good pragmatic argument for forcing it to use the POSIX locking? Maybe there is and I'm not seeing it. Both you and Corrina have stated there will be problems with other Cygwin programs, but nobody has mentioned anything specific. Anyway, that's my $0.02, which is probably not even worth that. -- David Rothenberger ---- daveroth AT acm DOT org Recursion n.: See Recursion. -- Random Shack Data Processing Dictionary -- 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