Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: <000d01c2cde5$ac861b30$78d96f83@pomello> From: "Max Bowsher" To: "Nigel Stewart & Fiona Smith" , "cygwin" References: <20030204194653 DOT A5738 AT thebrain DOT conmicro DOT cx> <20030204204803 DOT A6191 AT thebrain DOT conmicro DOT cx> <20030205033246 DOT GA4959 AT redhat DOT com> <20030205111822 DOT B9661 AT thebrain DOT conmicro DOT cx> <3E414A63 DOT 6060608 AT nigels DOT com> <033101c2cd3f$4f2936d0$78d96f83 AT pomello> <3E42608E DOT 1070507 AT nigels DOT com> Subject: Re: Packaging software built with cygwin Date: Thu, 6 Feb 2003 13:43:04 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Nigel Stewart & Fiona Smith wrote: > Fair enough, I like using Cygwin-the-environment, but > feel restricted in terms of deploying binaries into > a non-cygwin environment. Even though the Cygwin > installation procedure has been greatly enhanced and > streamlined, in my opinion Cygwin is too heavy-weight for > an average computer user to install and administer. I agree that Cygwin is a very bulky solution if you only want to be able to run one program (ssh, or rsync, for example). > So rather than upsetting the Cygwin faithful, would > it be better to expand the support POSIX subset for > mingw, rather than making Cygwin an easily managed > light-weight dependency. Those are 2 different paths to the same goal. However, if you worked at it from the Cygwin end, the resulting code would be GPL. Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/