FW: Cygwin patches into X (fwd)
Mon Sep 27 10:26:00 GMT 1999
I don't understand. Was this person responsible for submitting
the __CYGWIN__ patches to the code base?
On Mon, Sep 27, 1999 at 08:01:52AM -0400, Suhaib Siddiqi wrote:
>Following message may be of interest to others.
>> Feel free to forward to the list if you like.
>> ------- Forwarded Message
>> From: Branden Robinson <email@example.com>
>> Date: Wed, 15 Sep 1999 19:00:17 -0400
>> To: Nils Lohner <firstname.lastname@example.org>
>> Cc: email@example.com
>> Subject: Re: Unidentified subject!
>> Message-ID: <19990915190017.B11098@ecn.purdue.edu>
>> References: <199909151510.RAA00999@bernin.grnbl_domain>
>> Mime-Version: 1.0
>> User-Agent: Mutt/1.0pre2i
>> In-Reply-To: <199909151510.RAA00999@bernin.grnbl_domain>
>> - --9Ek0hoCL9XbhcSqy
>> Content-Type: text/plain; charset=us-ascii
>> Content-Transfer-Encoding: quoted-printable
>> On Wed, Sep 15, 1999 at 05:10:33PM +0200, Nils Lohner wrote:
>> > Someone has patches to allow XF86 to be built under Windoze
>> > with cygwin, and the XF people are reluctant to let
>> them in due to
>> > commercial interestes, i.e. the finished X server
>> binaries can't be bundl=
>> > with other software. Where do I find a clue bat large
>> enough to change
>> > this thinking? Please have a lok at the mail below and
>> let me know what =
>> > can possibly do.
>> Yes, I saw the gigantic flamewar on xfree86-devel about
>> this, which was
>> hopelessly entagled with what I'm sure is the thousandth
>> iteration of a
>> BSD vs. GPL licensing flamewar on that list.
>> > My thinking: the patches do not force you to use cygwin
>> to compile, but=
>> > rather just enable it for those who want it, and so I
>> don't see any reaso=
>> > why the XF people should object to the patches. They
>> enhance and do not=
>> > limit in any way. If someone else wants to posrt it to
>> a compiler with a=
>> > different license, noone is stopping them.
>> That's true.
>> > This is really frustrating me, people being this narrow
>> minded (what's th=
>> > politically correct term for that? :) and I'm hoping
>> people here will hav=
>> > some useful suggestions.
>> Uh, this mailing list is brand new and pretty limited in
>> scope. (See the
>> charter at < http://www.debian.org/~branden/ >.)
>> If some folks here want to form or join a coalition about
>> this, I don't
>> care, but I personally have too many irons in the fire as
>> is and don't have
>> much personal interest in such a thing (though you can be
>> sure I'd use it
>> if it saw the light of day).
>> Ultimately I think the best way to change XFree86's mind
>> on things like
>> this is:
>> 1) Make very sure all these cygwin changes are
>> MIT-licensed. I don't see
>> why this should be such a big deal as the X source
>> base already
>> supports tons of proprietary compilation
>> environments already.
>> 2) If they don't listen, fork. The sound of moving
>> feet is a powerful
>> motivator. When interests diverge, this is often
>> the best thing to
>> Point 2 has problems with the XFree86 membership
>> agreement, though,
>> especially if the current patches are based against the
>> CVS version of the
>> XFree86 code. Then again, with 3.9.16 out, how different
>> can it be?
>> I don't really have much more advice than that. I also
>> don't feel this
>> topic is terribly germane to this list, so if interested
>> parties from this
>> list would consider mailing each other about I'd appreciate it.
>> Sorry to sound so uninterested but I really just have too
>> much on my plate
>> to concern myself with XFree86 for Windows. I hope you
>> can sympathize.
>> - --=20
>> G. Branden Robinson | You don't just
>> decide to break Kubrick=
>> Debian GNU/Linux | code of silence and
>> then get drawn away
>> firstname.lastname@example.org | from it to a
>> discussion about cough
>> cartoon.ecn.purdue.edu/~branden/ | medicine.
>> - --9Ek0hoCL9XbhcSqy
>> Content-Type: application/pgp-signature
>> - -----BEGIN PGP SIGNATURE-----
>> Version: 2.6.3a
>> - -----END PGP SIGNATURE-----
>> - --9Ek0hoCL9XbhcSqy--
>> - --
>> To UNSUBSCRIBE, email to email@example.com
>> with a subject of "unsubscribe". Trouble? Contact
>> ------- End of Forwarded Message
More information about the Cygwin-xfree