public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Patrick Lauer <gentoo@toso-digitals.de>
To: Paul de Vrieze <pauldv@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Winex-cvs being removed from portage?
Date: 25 Jul 2003 11:49:18 +0200	[thread overview]
Message-ID: <1059126558.1438.18.camel@localhost> (raw)
In-Reply-To: <200307250813.18153.pauldv@gentoo.org>

On Fri, 2003-07-25 at 08:13, Paul de Vrieze wrote:

> To make it clear.
> 
> 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.
Wine is now GPL afaik.

> Further we have been asked 
> not to provide the cvs ebuild. This makes it easy for people to use the cvs 
> version of winex, so getting winex without paying. The people making winex 
> still need to eat though, so if we continue to offer winex-cvs ebuilds a 
> consequence could be that they close up their cvs to protect their living, 
> and with that hurting a lot of innocent bystanders.
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. 

That's were Stallman and the GPL come in: The GPL keeps your work
available for all. Other licences may be abused.

>  They see their cvs access 
> as a way people can help contribute to winex, and get winex in return. They 
> don't mind people getting winex for free if those people help developing. The 
> way the gentoo ebuild works, makes it very easy for people to use the cvs 
> version without even thinking. Most of those people probably do not help 
> developing winex, and as such use a resource without paying for it.
It gives the community the patches made to wine. I dislike the 
whining of Transgaming because people use the product they got for free.

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.

Yust my 2 Eurocents,
Patrick Lauer


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-07-25  9:50 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 [this message]
2003-07-25 10:00               ` Patrick Kursawe
2003-07-25 11:54               ` Chris Gianelloni
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=1059126558.1438.18.camel@localhost \
    --to=gentoo@toso-digitals.de \
    --cc=gentoo-dev@gentoo.org \
    --cc=pauldv@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