This is the mail archive of the cygwin-xfree@cygwin.com mailing list for the Cygwin XFree86 project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

RE: suggestion


 Let the keyboard and harold Winx support stabilize then we will revisit
it.  I do plan on modifying setup.exe so user can install directly from web.
It will not be an issue with licensing.  If Licensing is not changing then
inclusion of binaries and sources should not be a problem.  
Since binaries linked to Cgwin1.dll require sources be avilable and it does
not conflicts with X license.

However, I do want to want to get international keyboard from Andrew and
harold Win9x support stbilized, then work on setup.exe.  At present XF86
consider Cygwin support under beta testing therefore it is not mentioned in
their README files and at their URL.

Suhaib

-----Original Message-----
From: Christopher Faylor
To: cygwin-xfree@cygwin.com
Cc: Corinna Vinschen
Sent: 4/3/2001 6:10 PM
Subject: Re: suggestion

On Tue, Apr 03, 2001 at 02:59:24PM +0200, Corinna Vinschen wrote:
>On Tue, Apr 03, 2001 at 08:15:01AM -0400, Suhaib Siddiqi wrote:
>> 
>> It cannot be integrated in core distribution of Cygwin.  Because of
>> conflicting
>> GPL ad X licenses, it took me months to pursue XF86 board members to
at
>> least integrate
>> Cygwin related patches in XF86.  We are allowed to distribute
binaries and
>> sources 
>> separate of Cygwin, but officially integrating XF86 in Cygwin will
start
>> arguments
>> with XF86 board members and may result in throwing away Cygwin
support.
>> 
>> Therefore, answer is no.  Cygwin/XFree86 will always exists an open
source
>> separate project.
>> Binaries will be covered under GPL because they link to Cygwin1.dll,
but
>> XF86 sources will
>> be under X Consortium license, which means if you could get it
compile
>> without Cygwin1.dll
>> linking then your binaries will not be under GPL... which is fair
enough.
>
>That's a somewhat weird decision of the X Consortium. Putting the
>package into the Cygwin distro doesn't change the licensing terms
>of the sources.
>
>Jus as example, the OpenSSH sources aren't suddenly GPL'd only
>due to the fact that they are in the same directory as the OpenSSH
>Cygwin binaries. They will of course remain BSD licensed.

Yeah.  I really don't see how anyone could object to the fact that we
would allow a person to run "setup.exe" to download the X sources rather
than grab them from our web site.

We aren't going to include X in the Cygwin distribution until it
setup.exe has matured a little but it has always been one of my goals to
include this in a cygwin distribution.

I wasn't aware that there were any issues with this.  We certainly
wouldn't
change the licensing terms so I don't see how there could be issues with
this.

cgf


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]