Message-ID: <50AD2E36.6000002@tiscali.co.uk>
Date: Wed, 21 Nov 2012 19:40:38 +0000
From: David Stacey <drstacey AT tiscali DOT co DOT uk>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121029 Thunderbird/16.0.2
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] Updated: sqlite3-3.7.13-1
References: <announce DOT 5029275C DOT 4040009 AT etr-usa DOT com> <1353415897 DOT 5592 DOT 4 DOT camel AT YAAKOV04> <50AD20AD DOT 2090908 AT etr-usa DOT com>
In-Reply-To: <50AD20AD.2090908@etr-usa.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Note-from-DJ: This may be spam

On 21/11/12 18:42, Warren Young wrote:
> On 11/20/2012 05:51, Yaakov (Cygwin/X) wrote:
>> On Mon, 2012-08-13 at 10:12 -0600, Warren Young wrote:
>>> This is a *test* version which reverts the patch added to 3.7.12.1-1,
>>> which caused problems with Subversion as a side effect, particularly in
>>> systems using non-Cygwin programs with their svn checkout trees.
>>
>> And in so doing, removed several APIs which were added in 3.7.12.1,
>> breaking other packages which used them once they were made available.
>> Compatibility with Windows shouldn't come before backwards compatibility
>> for Cygwin packages.
>
> Okay, that makes a second vote for principle in four months.  (The 
> other being Corinna's.)  Add to that the original Achim Gratz vote for 
> "Unix mode," which carries more weight since it was accompanied by an 
> actual example of problems.
>
> Over a shorter period, I've received 16 upvotes on my explanation[1] 
> of the problem and its potential solutions.  And, the invitation for 
> comment I have at the end of that explanation has elicited no comment 
> at all.

I'm reluctant to chip into this discussion because there are probably 
some strong opinions on both sides. However, my opinions won't count for 
anything unless I air them, so...

Whilst I am relatively new to these mailing lists, I have been using 
Cygwin for many, many years. I have had to resolve a few conflicts with 
other tools over that time - such as disabling my webcam when the driver 
clashed with Cygwin's g++, and even now I have to disable my anti-virus 
when running setup.exe. These things I tolerate.

However, any conflict with TortoiseSVN is a different matter.

I am a professional software engineer, and Cygwin is one of the tools I 
use for my day job. Cygwin is great because it gives me a little Linux 
loveliness in a big bad Windows world. But I don't use Cygwin in 
isolation - I have many development tools that I use in a Windows 
environment, and, yes, one of those is TortoiseSVN.

Cygwin /has/ to function alongside the other development tools I use - 
if it can't then I lose interest rapidly. And that means I need Cygwin 
svn and TortoiseSVN to play nicely.

Now, I understand the desire for POSIX purity - such aims are laudable 
and highly commendable. However, when such ideals stand between me and 
getting paid then I take a different view. To put it bluntly, I really 
don't care if Cygwin svn uses POSIX locks, Windows locks or anyone 
else's locks - as long as it works.

I rather suspect that I am not alone and there are other Cygwin users in 
a similar situation.

Apologies for the rant,

Dave.


--
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