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:13:12 -0400 [thread overview]
Message-ID: <1127326392.30787.64.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <3f85ef27050921105464c82c51@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1519 bytes --]
On Wed, 2005-09-21 at 18:54 +0100, José Carlos Cruz Costa wrote:
> 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.
Umm... no. An ebuild is just a recipe for fetching/building a package.
It isn't the same as modification and redistribution (ala RPM) in any
way. It is *nothing* like tainting the kernel and this conversation has
*nothing* to do with what I asked an opinion on. I'm trying to ask a
technical opinion on a technical issue. There's no need to pull in any
political garbage into the discussion, as that only fans the flames.
> 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.
Those people are the exact reason I am wanting to do this. Right now,
they see "License: DOOM3" when they do an "emerge -S"... I'm
proposing they would see a "License: DOOM3 commercial" instead.
Anyway, please try to refrain from hijacking my thread into some
pseudo-political stance. I'm not making one or asking for one. I'm
asking for acceptance on a technical solution for some users that allows
them to make a political decision, without making any decisions for
them.
--
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:19 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
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 [this message]
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=1127326392.30787.64.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