From: "Paul Smith" <pausmith@nortelnetworks.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] No XFree86 w/ new license
Date: 19 Feb 2004 17:49:25 -0500 [thread overview]
Message-ID: <vpdrvfm265xm.fsf@lemming.engeast.baynetworks.com> (raw)
In-Reply-To: <40353473.7090809@gentoo.org>
%% Stewart Honsberger <blkdeath@gentoo.org> writes:
sh> Donnie Berkholz wrote:
>>> Could someone plz point me to those words in new version which cause
>>> all the troubles?
>> OK, let me lay it out as concisely as possible.
>> 1) XFree86 license 1.1 _requires_ attribution with other third-party
>> attributions.
>> 2) This requirement is an additional restriction beyond what the GPL
>> itself restricts.
>> 3) The GPL prohibits any additional restrictions.
>> From these three points we conclude:
>> 4) The XFree86 license 1.1 is incompatible with the GPL.
sh> So the only problem with this whole mess is that the XFree people
sh> want us to give them credit in the same place and mannar as we
sh> already give other third parties credit?
No. In fact RMS was recently quoted on this subject as saying that the
request for attribution is not in itself a bad thing:
http://www.ofb.biz/modules.php?name=News&file=article&sid=297
The problem is exactly what Donnie says: the license is not compatible
with the GPL.
Much of the software distributed on your distribution is licensed under
the GPL, including many X applications. If the license of the X
libraries is not compatible with the GPL, then no one can distribute
them together.
Qt, for example, is only distributable without royalties under the GPL,
which means that no Qt libraries can be linked with X libraries under
the new license (unless you pay $$ to TT). I'm sure the KDE folks, at
the least, would not be happy about that.
sh> XFree86, pending a replacement, is the only thing giving Linux any
sh> credibility as a desktop operating system. Therefore, I would say
sh> it's rather an integral part of the acceptance of our distribution
sh> and OS as a whole. As such, I wouldn't think a one-liner in a
sh> README, INSTALL, or product literature is such a Big Stinking
sh> Deal.
No one said it was.
sh> It's not like they're making the software non-free, they're not
sh> demanding royalties, they're not prohibiting the software from
sh> being distributed, they're just asking for due credit.
Yes. The problem is the way they are doing it.
sh> Think of it from their point of view; when some Joe Schmoe starts
sh> up X, they see what - KDE or Gnome. What do they think is
sh> providing them a GUI? KDE or Gnome. They don't realize that
sh> underneath these environments is a hard-working old man spewing
sh> 2D/3D rendering instructions to their video cards and keeping the
sh> windows from falling off the screen. All they want is a small
sh> heads-up. Is that so wrong?
You're arguing a straw man.
sh> I'd really like a point-by-point dissection of the objectionable
sh> license changes
Donnie provided one, and you even quoted it above.
It may seem a little thing to you, but free software folks care a lot
about these kinds of things. We rely heavily on copyright and licenses,
and so we try to respect both the letter _and_ the intent of each one
that we use.
sh> Thank-you in advance for helping us understand a potentially
sh> earth-shattering situation over which we seem to have no control.
Really, I think you're overstating the enormity of the situation. We
still have all the distribution up to 4.4rc2. X has been forked before
(where do you think XFree came from in the first place?), and it can
easily be forked again if it comes to that.
But, I doubt it will come to that.
--
-------------------------------------------------------------------------------
Paul D. Smith <psmith@nortelnetworks.com> HASMAT--HA Software Mthds & Tools
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions---Nortel Networks takes no responsibility for them.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-02-19 22:49 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 3:17 [gentoo-dev] No XFree86 w/ new license Donnie Berkholz
2004-02-17 3:37 ` Donnie Berkholz
2004-02-17 4:25 ` Donnie Berkholz
2004-02-18 14:50 ` CJ Kucera
2004-02-18 14:56 ` Paul de Vrieze
2004-02-18 15:13 ` CJ Kucera
2004-02-18 16:50 ` Donnie Berkholz
2004-02-18 17:50 ` CJ Kucera
2004-02-18 18:57 ` [gentoo-dev] " James H. Cloos Jr.
2004-02-18 19:19 ` CJ Kucera
2004-02-18 19:07 ` [gentoo-dev] " Donnie Berkholz
2004-02-18 19:09 ` Chris Gianelloni
2004-02-18 19:18 ` CJ Kucera
2004-02-18 20:16 ` Paul de Vrieze
2004-02-18 20:56 ` Andrew Cowie
2004-02-18 22:16 ` Donnie Berkholz
2004-02-19 5:07 ` CJ Kucera
2004-02-19 2:57 ` Clay Culver
2004-02-17 7:22 ` Spider
2004-02-17 8:19 ` Donnie Berkholz
2004-02-19 20:39 ` Jason Rhinelander
2004-02-19 20:44 ` Donnie Berkholz
2004-02-20 14:36 ` Daniel Armyr
2004-02-20 15:10 ` Nathaniel McCallum
2004-02-20 11:04 ` Paul de Vrieze
2004-02-20 11:47 ` Peter Robinson
2004-02-20 13:16 ` Eldad Zack
2004-02-19 20:43 ` Svyatogor
2004-02-19 20:40 ` Donnie Berkholz
2004-02-19 22:10 ` Stewart Honsberger
2004-02-19 22:18 ` Tal Peer
2004-02-19 22:43 ` Luke-Jr
2004-02-20 4:59 ` Donnie Berkholz
2004-02-20 5:24 ` Luke-Jr
2004-02-20 5:37 ` Mike Frysinger
2004-02-19 22:49 ` Paul Smith [this message]
2004-02-19 22:56 ` George Shapovalov
2004-02-22 20:50 ` [gentoo-dev] " Drake Wyrm
2004-02-22 21:33 ` Jon Portnoy
2004-02-22 21:50 ` Jay Maynard
2004-02-22 22:29 ` Jon Portnoy
2004-02-23 3:20 ` Luke-Jr
2004-02-23 3:33 ` Jay Maynard
2004-02-23 3:47 ` Luke-Jr
2004-02-23 3:12 ` Luke-Jr
2004-02-22 21:58 ` Paul de Vrieze
2004-02-22 22:09 ` Donnie Berkholz
2004-02-25 6:32 ` [gentoo-dev] No " Jason Stubbs
2004-02-25 10:54 ` Brian Jackson
2004-02-25 12:27 ` Jason Stubbs
2004-02-25 13:12 ` John Nilsson
2004-02-25 13:35 ` Jay Maynard
2004-02-25 13:40 ` Luke-Jr
2004-02-25 13:48 ` Jay Maynard
2004-02-25 14:22 ` Paul Smith
2004-02-25 16:13 ` Luke-Jr
2004-02-27 18:17 ` Jon Portnoy
2004-02-27 18:33 ` Jay Maynard
2004-02-27 18:44 ` Jon Portnoy
2004-02-27 19:22 ` Paul de Vrieze
2004-02-27 20:21 ` Jay Maynard
2004-02-27 20:43 ` Michael Cummings
2004-02-25 13:43 ` Paul Smith
2004-02-25 14:44 ` John Robinson
2004-02-26 13:28 ` Svyatogor
2004-02-26 13:21 ` Donnie Berkholz
2004-02-26 13:43 ` Svyatogor
2004-02-26 15:36 ` Matthew Kennedy
2004-02-26 15:57 ` Stewart
2004-02-26 16:05 ` Donnie Berkholz
2004-02-27 3:08 ` Matthew Kennedy
2004-02-27 7:40 ` Brad Laue
2004-02-27 7:51 ` Donnie Berkholz
2004-02-27 9:10 ` Phil Richards
2004-02-27 9:40 ` John Nilsson
2004-02-27 9:52 ` Phil Richards
2004-02-27 10:25 ` John Nilsson
2004-02-27 10:56 ` Tom Wesley
2004-02-27 12:39 ` Chris Gianelloni
2004-02-27 11:32 ` Svyatogor
2004-02-27 12:15 ` Jay Maynard
2004-02-27 12:35 ` Chris Gianelloni
2004-02-27 13:47 ` John Nilsson
2004-02-27 12:29 ` Chris Gianelloni
2004-02-27 13:57 ` John Nilsson
2004-02-27 12:21 ` Chris Gianelloni
2004-02-26 13:24 ` Patrick Kursawe
2004-02-26 13:29 ` Paul de Vrieze
2004-02-26 13:42 ` Toby Dickenson
2004-02-26 13:52 ` Paul de Vrieze
2004-02-26 16:14 ` Donnie Berkholz
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=vpdrvfm265xm.fsf@lemming.engeast.baynetworks.com \
--to=pausmith@nortelnetworks.com \
--cc=gentoo-dev@lists.gentoo.org \
/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