From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] "Commercial" software in portage
Date: Wed, 21 Sep 2005 14:15:06 -0400 [thread overview]
Message-ID: <1127326506.30787.67.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <1127325642.7832.32.camel@Memoria.anyarch.net>
[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]
On Wed, 2005-09-21 at 14:00 -0400, Daniel Ostrow wrote:
> On Wed, 2005-09-21 at 18:54 +0100, José Carlos Cruz Costa wrote:
> > Hi everybody,
> >
> > If it's commercial, the company in question should (and must) allow an
> > ebuild for is product, like what happens with rpms and other packages.
> > Adding commercial ebuilds to portage is like tainting the kernel with
> > binary drivers.
> >
> > Maybe a better solution comes with gensync? If companies want ebuilds,
> > sure. They go to the "commercial" portage. Hell, even put a price on
> > maintaining those ebuilds.
> >
> > Remember that are a lot of people that don't want to use that kind of
> > software. There are people that doesn't have even xorg and have to
> > sync all the ebuilds from portage.
>
> This is what rsync excludes are for...there is no good reason to remove
> things like doom3 and UT2k4 from the tree for the sole reason that they
> are commercial packages. You don't want them...fine...exclude them.
...or just don't emerge them. It isn't like we're sending SpanKY to
your house to force you to play them. Many commercial packages are
designed to be used on RPM-based distributions, so many users find out
ebuilds invaluable for these things.
The whole point I am trying to make is that I am *not* going to make any
sort of political decision, but rather implement a slight change
tree-wide to empower users to make decisions of that sort for
themselves.
--
Chris Gianelloni
Release Engineering - Strategic Lead
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-09-21 18:21 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 17:31 [gentoo-dev] "Commercial" software in portage Matthew Marlowe
2005-09-21 17:54 ` José Carlos Cruz Costa
2005-09-21 18:00 ` Daniel Ostrow
2005-09-21 18:15 ` Chris Gianelloni [this message]
2005-09-22 8:26 ` Philippe Trottier
2005-09-23 14:42 ` Brian Harring
2005-09-23 15:06 ` Jason Stubbs
2005-09-21 18:08 ` Daniel Ostrow
2005-09-21 18:13 ` Chris Gianelloni
2005-09-21 17:57 ` Chris Gianelloni
2005-09-21 22:55 ` Lance Albertson
2005-09-22 13:30 ` Chris Gianelloni
2005-09-22 16:46 ` Brian Harring
2005-09-22 17:30 ` Chris Gianelloni
2005-09-22 20:29 ` Brian Harring
2005-09-22 21:09 ` Chris Gianelloni
2005-09-22 21:57 ` warnera6
2005-09-22 22:01 ` Ciaran McCreesh
2005-09-23 13:09 ` Chris Gianelloni
2005-09-23 1:38 ` Jason Stubbs
2005-09-23 13:28 ` Chris Gianelloni
2005-09-23 14:08 ` Jason Stubbs
2005-09-23 14:59 ` Chris Gianelloni
-- strict thread matches above, loose matches on Subject: below --
2005-09-21 13:51 Chris Gianelloni
2005-09-21 20:15 ` Paweł Madej
2005-09-21 22:31 ` Marius Mauch
2005-09-22 8:14 ` Thierry Carrez
2005-09-22 13:34 ` Chris Gianelloni
2005-09-22 13:28 ` Chris Gianelloni
2005-09-22 15:37 ` Georgi Georgiev
2005-09-22 15:54 ` Chris Gianelloni
2005-09-22 16:56 ` Cory Visi
2005-09-22 17:13 ` Matti Bickel
2005-09-22 17:04 ` 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=1127326506.30787.67.camel@cgianelloni.nuvox.net \
--to=wolf31o2@gentoo.org \
--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