From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5424 invoked by alias); 19 Dec 2005 12:20:06 -0000 Received: (qmail 27159 invoked by uid 22791); 19 Dec 2005 09:29:40 -0000 X-Spam-Status: No, hits=-0.4 required=5.0 tests=AWL,BAYES_50 X-Spam-Check-By: sourceware.org From: =?iso-8859-1?Q?Tevfik_Karag=FClle?= To: Subject: Re: 1NIWGYC.DLL ?? Date: Mon, 19 Dec 2005 12:20:00 -0000 Message-ID: <006f01c6047e$b68137f0$2602a8c0@itefixb> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcYEfrWIDZ0HHgBdSQC3jfjhJBRzFw== Mailing-List: contact cygwin-licensing-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: cygwin-licensing-owner@cygwin.com X-SW-Source: 2005-q4/txt/msg00012.txt.bz2 > I don't know what you mean by "cygwin development environment" but, > AFAIK, you are not developing the cygwin DLL. What do you call if I use a cygwin environment for development and testing ? Such environments should be separated from production environments where Openshh/rsync could be used as elements. That's my point !!! > downloading the latest version of the cygwin distribution and don't want > to somehow destabilize your openssh setup then it seems like working > with the setup.exe and openssh maintainers is the best way to accomplish > this. I can only say that there are (should be!!) other ways to do the same thing. In addition, as I wrote in my previous post, the best solution would be to use a cygwin setup, which allows several separated environments. Platform virtualization is a hot topic nowadays. Why can't cygwin also offer that functionality? > It really sounds like you are interested in providing workarounds for > what you perceive to be problems with the cygwin distribution rather > than working towards fixing the problems. Sorry, I don't agree with you. Maybe, I fix some problems which have low priority in your list. When it comes to workarounds, they will always exist. > I suspect that your efforts will just serve to confuse people and so > I'm not happy with the way you are proceeding and I will certainly > publicly express my dissatisfaction the first time someone posts > a question about "your" version of openssh and whatever-you-call-the-dll > on the cygwin list. Confusing people ? How can I do that with developing an installer installing a fully operational openssh server and make it ready for use within one minute? Disturbing your forums happened only once during the copssh lifetime. BTW, The full blown cygwin installation had the same problem. I've just tried to express a need. I feel that I don't deserve your comments above. > So, yes, this is a GPL project and you can take the software, > rename it and massage it to do whatever you want with it. That does not mean > that it is the right thing to do or that your efforts will be appreciated by > the people who are providing the software, however. Both Copssh and Cwrsync are free software. As of december 2005, they are being downloaded ca. 300 times daily and I get many mails from users expressing their appreciations. What's the right thing to do ? To continue with this effort? To express a growing demand and a possible solution to cygwin developers ? I did it both !!!! Tev