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]
Other format: [Raw text]

Re: seperate xfree project on sourceforge


----- Original Message -----
From: "Christopher Faylor" <cgf@redhat.com>
To: <cygwin-xfree@cygwin.com>
Cc: <rasjidw@bigpond.com>
Sent: Tuesday, November 20, 2001 6:03 AM
Subject: Re: seperate xfree project on sourceforge


> On Mon, Nov 19, 2001 at 07:05:47PM +1100, Matthew Donald wrote:
> >Hi,
> >
> >I been keeping winfree86 with a very low profile since its still not
really
> >ready for release even as alpha code.  However since Ralf Habacker
stumbled
> >across it, it's time to 'fess up.
> >
> >Winfree86 does not fork either the cygwin or xfree codebase.  It is much
> >more akin to a distribution rather than new product.
> >
> >Yes, winfree86 does contain some new code, but I can't see how it can
easily
> >be incorporated into the existing project.  The problem is that this code
is
> >built using proprietary tools.  Although winfree86 is GPL'ed, it isn't a
> >clean GPL.
> >
> >Why?  Well, integrating xfree into win32 cleanly is going involve COM
> >objects.  AFAIK, gcc doesn't support COM (and the thought of doing COM in
> >raw C is pretty revolting). Gcc wont work with MFC or ATL, and anyway
both
> >of those involve Microsoft licenses.  So that leaves a choice of using a
> >Microsoft/Borland C compiler (do any other C compilers come with a
MFC/ATL
> >license?) or using a high-level language such as VB or Delphi.
>
> So, it sounds like you have some immediate licensing issues that could
> cause this project to be stillborn.  How are you going to work around
> the fact that cygwin requires open source?

Cygwin only requires the project source to be available.  GPL does not
require compiler source to be available (unless the compiler as opposed to
the project is subject to GPL).  As I made clear in my previous post, there
are no suitable open source tools available to code COM objects (unless
someone is going to make a MFC or ATL clone for gcc available RSN :-)

> >Rasjid Wilcox had a very similar idea to winfree86 named winxterm (see
> >http://lasp.sourceforge.net/winxterm/ ).  He has already produced a
minimal
> >cygwin + xfree of about 4mb.  If we can integrate the two projects
winfree86
> >(or whatever its called) will be available much sooner.
>
> This sounds like YA ill-conceived fork.  And, oh joy, oh rapture, it is
also
> YA GPL violation.
>
> I've Cc'ed Rasjid.  Rasjid -- you need to provide the sources for the
> binary packages that you are providing, in compliance with the GPL.  Just
> providing a link to cygwin.com is not sufficient.
>


Yes the source code will be made available.

Please keep your flames to yourself.  Don't you have real problems to worry
about?


Matthew


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