From: Jim Kingdon <kingdon@redhat.com>
To: per@bothner.com
Cc: cgf@cygnus.com, overseers@sourceware.cygnus.com
Subject: Re: cygwin-xfree
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <200005041135.HAA17116@devserv.devel.redhat.com> (raw)
In-Reply-To: <m2snvy3kmy.fsf@kelso.bothner.com>
> How is this different from creating a port of X that runs under SunOS?
At the risk of starting/continuing Yet Another Pointless Licensing
Flamewar....
The SunOS libc and other required libraries aren't under a viral
license (some proprietary compiler vendors, at least in the PC world,
tried this some years ago, but they didn't get away with it. The most
amusing crash and burn being the TI-99/4 which wanted developers to
pay to develop products on that platform, sign NDA's, etc. With the
predictable result - no applications and the eventual death of the
platform).
Now whether that has anything to do with the difficulty in getting the
cygwin XFree patches merged in, I don't know. Over in Cristian's
group (don't remember who specifically builds the XFree RPMs for the
Red Hat Linux product but someone over there) they ship about 40
patches to XFree (last I looked), and licensing isn't an issue in that
context.
WARNING: multiple messages have this Message-ID
From: Jim Kingdon <kingdon@redhat.com>
To: per@bothner.com
Cc: cgf@cygnus.com, overseers@sourceware.cygnus.com
Subject: Re: cygwin-xfree
Date: Thu, 04 May 2000 04:35:00 -0000 [thread overview]
Message-ID: <200005041135.HAA17116@devserv.devel.redhat.com> (raw)
Message-ID: <20000504043500.EvtEPsaVYPUqA4OQj0MiiNKOsY6FV4XXEw9-_TWhlx0@z> (raw)
In-Reply-To: <m2snvy3kmy.fsf@kelso.bothner.com>
> How is this different from creating a port of X that runs under SunOS?
At the risk of starting/continuing Yet Another Pointless Licensing
Flamewar....
The SunOS libc and other required libraries aren't under a viral
license (some proprietary compiler vendors, at least in the PC world,
tried this some years ago, but they didn't get away with it. The most
amusing crash and burn being the TI-99/4 which wanted developers to
pay to develop products on that platform, sign NDA's, etc. With the
predictable result - no applications and the eventual death of the
platform).
Now whether that has anything to do with the difficulty in getting the
cygwin XFree patches merged in, I don't know. Over in Cristian's
group (don't remember who specifically builds the XFree RPMs for the
Red Hat Linux product but someone over there) they ship about 40
patches to XFree (last I looked), and licensing isn't an issue in that
context.
next prev parent reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 cygwin-xfree Chris Faylor
2000-05-03 19:18 ` cygwin-xfree Chris Faylor
2000-12-30 6:08 ` cygwin-xfree Jason Molenda
2000-05-03 19:45 ` cygwin-xfree Jason Molenda
2000-12-30 6:08 ` cygwin-xfree Chris Faylor
2000-05-03 19:53 ` cygwin-xfree Chris Faylor
2000-12-30 6:08 ` htdig, was cygwin-xfree Frank Ch. Eigler
2000-05-03 20:23 ` Frank Ch. Eigler
2000-12-30 6:08 ` Hans-Peter Nilsson
2000-05-06 2:43 ` Hans-Peter Nilsson
2000-12-30 6:08 ` cygwin-xfree Andrew Cagney
2000-05-03 19:30 ` cygwin-xfree Andrew Cagney
2000-12-30 6:08 ` cygwin-xfree Jim Kingdon
2000-05-03 19:47 ` cygwin-xfree Jim Kingdon
2000-12-30 6:08 ` cygwin-xfree Chris Faylor
2000-05-03 19:34 ` cygwin-xfree Chris Faylor
2000-12-30 6:08 ` cygwin-xfree Jeffrey A Law
2000-05-04 9:07 ` cygwin-xfree Jeffrey A Law
2000-12-30 6:08 ` cygwin-xfree Tom Tromey
2000-05-03 19:59 ` cygwin-xfree Tom Tromey
2000-12-30 6:08 ` cygwin-xfree Chris Faylor
2000-05-03 20:07 ` cygwin-xfree Chris Faylor
2000-12-30 6:08 ` cygwin-xfree Per Bothner
2000-05-03 23:21 ` cygwin-xfree Per Bothner
2000-12-30 6:08 ` Jim Kingdon [this message]
2000-05-04 4:35 ` cygwin-xfree Jim Kingdon
2000-12-30 6:08 ` cygwin-xfree Tom Tromey
2000-05-03 20:09 ` cygwin-xfree Tom Tromey
2000-12-30 6:08 ` libstdc++-v3 things that still are not working correctly Benjamin Kosnik
2000-05-03 20:14 ` Benjamin Kosnik
2000-12-30 6:08 ` Jeffrey A Law
2000-05-03 22:33 ` Jeffrey A Law
2000-12-30 6:08 ` cygwin-xfree Chris Faylor
2000-05-03 20:22 ` cygwin-xfree Chris Faylor
2000-12-30 6:08 ` cygwin-xfree Jim Kingdon
2000-05-04 4:52 ` cygwin-xfree Jim Kingdon
2000-12-30 6:08 ` cygwin-xfree Chris Faylor
2000-05-04 7:48 ` cygwin-xfree Chris Faylor
2000-12-30 6:08 ` cygwin-xfree Bob Manson
2000-05-03 21:11 ` cygwin-xfree Bob Manson
2000-12-30 6:08 ` cygwin-xfree Jason Molenda
2000-05-04 13:19 ` cygwin-xfree Jason Molenda
2000-12-30 6:08 ` cygwin-xfree Jim Kingdon
2000-05-07 6:32 ` cygwin-xfree Jim Kingdon
2000-12-30 6:08 ` cygwin-xfree Stan Shebs
2000-05-21 22:19 ` cygwin-xfree Stan Shebs
2000-12-30 6:08 ` cygwin-xfree Mark Galassi
2000-05-22 6:15 ` cygwin-xfree Mark Galassi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200005041135.HAA17116@devserv.devel.redhat.com \
--to=kingdon@redhat.com \
--cc=cgf@cygnus.com \
--cc=overseers@sourceware.cygnus.com \
--cc=per@bothner.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).