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 Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 10 Jan 2002 13:40:19 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: ksh on cygwin Message-ID: <20020110184019.GE26493@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <200201101618 DOT g0AGIfs08384 AT dymwsm15 DOT mailwatch DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200201101618.g0AGIfs08384@dymwsm15.mailwatch.com> User-Agent: Mutt/1.3.23.1i On Thu, Jan 10, 2002 at 11:18:04AM -0500, Fleischer, Karsten (K.) wrote: >>If you've actually looked at the UWIN sources, this is not enough. >>IANAL either, but I believe that this means you've been tainted. That >>means that we can't use your patches. Sorry. > >I've never had the chance to look at the UWIN sources. It's >proprietary. As I said before, the UWIN developers explained the >concepts verbally to me, no source code involved. > >The AST tools and libraries, which form the basis for the UWIN _tools_ >(not the UNIX emulation itself) are open source. I rewritten some >things from those sources (but from memory). > >>I hope I am misinterpreting what you said incorrectly... > >:-P I'm not sure but I don't think it matters if the sources are proprietary. Maybe this is getting incredibly picky but if you adapted algorithms from other non-GPL compliant programs then that is probably an issue, too. This wouldn't be an issue for the Berkeley license, though. I don't know what the AST tools use for licensing. cgf -- 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/