From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Winex-cvs being removed from portage?
Date: 25 Jul 2003 07:54:55 -0400 [thread overview]
Message-ID: <1059134094.24531.27.camel@vertigo> (raw)
In-Reply-To: <1059126558.1438.18.camel@localhost>
On Fri, 2003-07-25 at 05:49, Patrick Lauer wrote:
> > winex is not GPL, I believe it has a MIT-X license.
> Wine was under a BSD-style license until the Transgaming people started
> selling it without giving back to wine.
Actually, it was X11 licensed. They changed the licensing not because
of Gavriel and Transgaming at all, but because of Lindows. Go check the
wine-devel archives to find the discussions.
> Wine is now GPL afaik.
LGPL, but close enough.
> Why should these people get money for using technology provided by the
> wine project?
> I know this sounds a lot like a flame, but they took the years of work
> of the wine project, added some value and started selling it.
Because the old wine license allowed it? There is no other reason.
Your comments here *are* a flame. Followed immediately by a praising of
the almighty GPL...
> That's were Stallman and the GPL come in: The GPL keeps your work
> available for all. Other licences may be abused.
There is plenty of reason for other licenses, otherwise they would not
exist. For example, if I wanted to create an open source application,
yet also create a feature-enhanced binary only version, a BSD license
would be a perfect choice for me to select.
> It gives the community the patches made to wine. I dislike the
> whining of Transgaming because people use the product they got for free.
Transgaming is no longer simply issuing "patches made to wine", but
rather a quite changed product that was *derived* from wine. This is a
major distinction. Transgaming made a simple request. Nobody is
whining but you.
> If they want Gentoo not to use the anonymous CVS in an automated
> fashion, ok, but why do they offer it? So I can develop their product?
> wtf? That feels very wrong to me. Like Microsoft Shared Source: You
> patch, we own.
If it feels wrong to you, then don't use it. Don't develop for them.
It is that simple. Microsoft's shared source is a poor example for
obvious reasons. I'm not even going to say any more than that because I
feel strongly against feeding trolls.
--
Chris Gianelloni
Developer, Gentoo Linux
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-07-25 11:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 5:08 [gentoo-dev] Winex-cvs being removed from portage? dean .
2003-07-23 5:42 ` Seemant Kulleen
2003-07-25 1:01 ` Andrew Cowie
2003-07-25 1:42 ` Brett I. Holcomb
2003-07-25 1:45 ` Nick Hadaway
2003-07-25 2:01 ` Chris Gianelloni
2003-07-25 3:47 ` Owen Gunden
2003-07-25 4:14 ` Mike Frysinger
2003-07-25 4:35 ` Luke-Jr
2003-07-25 14:31 ` Adrian Almenar
2003-07-26 0:20 ` Luke-Jr
2003-07-26 13:34 ` Chris Gianelloni
2003-07-25 6:13 ` Paul de Vrieze
2003-07-25 9:49 ` Patrick Lauer
2003-07-25 10:00 ` Patrick Kursawe
2003-07-25 11:54 ` Chris Gianelloni [this message]
2003-07-25 12:26 ` Patrick Lauer
2003-07-25 13:17 ` Chris Gianelloni
2003-07-25 14:06 ` Dan Armak
2003-07-25 10:53 ` Svyatogor
2003-07-25 11:38 ` Chris Gianelloni
2003-07-25 14:08 ` Thomas de Grenier de Latour
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=1059134094.24531.27.camel@vertigo \
--to=wolf31o2@gentoo.org \
--cc=gentoo-dev@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