Mail Archives: cygwin/2002/01/10/11:04:42
On Thu, Jan 10, 2002 at 10:50:46AM -0500, Fleischer, Karsten (K.) wrote:
> > http://cygwin.com/cygwin-ug-net/ntsec.html
> >
> > It's rather old and a bit badly maintained but it's basically still
> > correct.
>
> I've read it a long time ago...
I'm feeling flattered. :-)
> > One general question, though. How do these changes to handle things
> > like U/WIN collide with the propietary U/WIN license? We don't want
> > to have problems with AT&T suddenly. Especially we don't want to
> > have sources taken from U/WIN.
>
> No sources were taken from UWIN or from the AST libraries.
> I'm using UWIN quite a lot here at Ford, because I needed to use the MSVC++ compiler.
> I've found many bugs in UWIN and I have email contact with David and Glenn on a regular basis. They asked me if I could help out porting AST to Cygwin, because they didn't want to touch (or even read) the Cygwin sources for obvious copyright problems.
> The concepts I've taken from UWIN were explained to me by them verbally, so no source code involved here.
> Other portions are rewritten from the AST sources (which are open source, see http://www.research.att.com/sw/license/ast-open.html).
> I don't know if this license and the GPL collide
IANAL but AFAIK, they collide.
> , so I've rewritten the code from memory after looking at the sources.
> The differences are substancial, so no problem here either.
I think that's ok. "Rewritten" should be enough. IANAL, IANAL, ...
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin AT cygwin DOT com
Red Hat, Inc.
--
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/
- Raw text -