X-Spam-Check-By: sourceware.org Date: Tue, 3 Jul 2007 09:54:24 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] New package: brltty 3.8 Message-ID: <20070703075424.GI30973@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20070606192615 DOT GG22248 AT trixie DOT casa DOT cgf DOT cx> <2D9E96311DCA4C48BF185EA6928BC7BB01E1BD3E AT asc-mail DOT int DOT ascribe DOT com> <20070607115925 DOT GC3958 AT implementation> <20070702233210 DOT GD3759 AT interface DOT famille DOT thibault DOT fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20070702233210.GD3759@interface.famille.thibault.fr> User-Agent: Mutt/1.4.2.2i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Jul 3 01:32, Samuel Thibault wrote: > Hi, > > Samuel Thibault, le Thu 07 Jun 2007 19:59:25 +0800, a écrit : > > Phil Betts, le Thu 07 Jun 2007 12:14:33 +0100, a écrit : > > > Might I suggest a compromise? Create a new "Accessibility" group in > > > setup. It would (at least for now) be the first group > > > > That would be a fair compromise, yes. > > There was no more comment on this. Is this OK? In theory, yes. But I'm still not happy with the dependency to ws2_32. It should still go away and I don't see any reason to keep it. For using local named pipes you don't need winsock anyway, and for remote connections you should use Cygwin sockets. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/