This is the mail archive of the
mailing list for the Cygwin project.
Re: [ANNOUNCEMENT] New package: brltty 3.8
On Fri, Jun 08, 2007 at 11:05:19PM +0800, Samuel Thibault wrote:
>Christopher Faylor, le Fri 08 Jun 2007 10:42:49 -0400, a ?crit :
>> On Fri, Jun 08, 2007 at 03:57:20PM +0800, Samuel Thibault wrote:
>> >Christopher Faylor, le Thu 07 Jun 2007 15:01:46 -0400, a ?crit :
>> >>What about unix domain sockets in cygwin? It sounds like you think
>> >>they aren't available.
>> >As I already said several times, it must work with non-cygwin
>> >applications as well.
>> A unix domain socket used on stdin/stdout works with non-cygwin
>> It would really help if you provided an actual use case which
>> demonstrated what you are talking about.
>I'm a bit tired to re-explain all of this, I've already had to do it on
>other lists, it's really boring to go along all these arguments just
>once more... But since you really want some details, here are more:
You are not the only one who's tired. You have made some nonstandard
decisions in a package which is going into a distribution that I run. I
have no reason to trust your technical judgement on this since I don't
know you from Adam and you are not using precise technical terms which
would allow me to understand if you are just some idiot who randomly
types bits into a file until it compiles or a genius who has built the
absolute best implementation of a program given specific technical
>Brltty acts as a "braille display server": when an application not only
>wants to display their usual GUI, but also braille, it can connect to
>brltty for rendering braille (by sending "write" commands, and receiving
>"keypress" events). Thus stdin/stdout can't work since applications may
>want to keep their text GUI as it is and the initiative of establishing
>the connexion comes from the application anyway, not brltty.
>> Otherwise, you seem to be asking that we just trust you that brltty is
>> different from most other packages in the distribution and deserves
>> special dispensation.
>I'm not asking so big special dispensation. Why should cygwin
>applications be forced to use cygwin sockets?
Cygwin isn't just a bunch of nifty programs clumped together for the
delight and enjoyment of windows users. It's whole purpose in life is
to provide implementations of programs which use the linux/unix API.
If you are purposely bypassing the Cygwin API then you're asking for
special dispensation. Get over it.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html