Mail Archives: cygwin/2012/11/21/13:43:23
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.
All of this tells me that:
a) There are more people negatively affected by the "Unix mode" build of
Cygwin SQLite than are by building it in "Cygwin mode".
b) There aren't enough people who do care to have SQLite built in Unix
mode to comment knowledgeably about it.
As far as I'm concerned, Cygwin SQLite will remain built in Cygwin mode
until Cygwin has a way to conditionally request mandatory locks, so that
we may have our cake and eat it, too.
If you think I'm wrong, take the package from me, build it your way, and
deal with the backlash you'll receive as a result.
[1] http://stackoverflow.com/questions/11007024/
--
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
- Raw text -