This is the mail archive of the
mailing list for the Cygwin project.
Re: Mandatory file locking semantics
- From: Warren Young <warren at etr-usa dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 05 Jun 2013 13:33:18 -0600
- Subject: Re: Mandatory file locking semantics
- References: <51A7F547 dot 6020509 at etr-usa dot com> <20130531092228 dot GB30659 at calimero dot vinschen dot de> <51A900EF dot 2020606 at etr-usa dot com> <20130601105741 dot GC30659 at calimero dot vinschen dot de> <20130602103125 dot GE13934 at calimero dot vinschen dot de> <51ACD415 dot 2090709 at etr-usa dot com> <20130604084815 dot GD19572 at calimero dot vinschen dot de> <51AF6433 dot 5050104 at etr-usa dot com> <20130605170246 dot GD3250 at calimero dot vinschen dot de> <51AF7303 dot 8060303 at etr-usa dot com> <20130605181516 dot GE3250 at calimero dot vinschen dot de>
On 6/5/2013 12:15, Corinna Vinschen wrote:
Actually, adding this stuff to Cygwin took almost four days of my
life as it is today.
Understood. Likewise, because I am not full-time on Cygwin SQLite, it's
taken similar amounts of time from me, which is why I'm ignoring your
xidepend complaints right now. :)
So far it's not even clear if you really can use it in sqlite.
That's definitely a possibility. I'll be posting my thoughts on that in
another part of the thread.
I hope that even if this doesn't end up helping SQLite, though, that the
code is still useful enough to stay in the DLL. I can't be the only one
who has ever had such interop problems.
Given all that, I'd appreciate if you'd first test if the whole effort
was even worth it.
Okay. -2 packages are built now. Announcement elsewhere.
Does that make sense, at least a bit?
Thank you for taking the time to explain.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple