From: "Rick \"Zero_Chaos\" Farina" <zerochaos@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: linux-firmware
Date: Wed, 20 Feb 2013 11:19:41 -0500 [thread overview]
Message-ID: <5124F79D.6010309@gentoo.org> (raw)
In-Reply-To: <20772.33119.636728.864172@a1i15.kph.uni-mainz.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/20/2013 02:55 AM, Ulrich Mueller wrote:
I am going to respond here because it makes the most sense to me.
> I mostly agree. However, there are not two, but three classes of
> licenses for firmware images:
>
> 1. Free software
> 2. Non-free, but can be redistributed
> 3. Cannot be redistributed
>
> The split between 2 and 3 is the more important one, because we cannot
> mirror things under 3.
I completely agree. I will HAPPILY divide the ebuild up with a nonfree
(or other suggested SANE use flag) to denote the difference between 1
and 2. None of this is under contest, this choice is all but too easy.
Depending on the licensing issues which arise I may even add in a
separate ebuild.
The issue come in with number 3. Adding a bindist use flag for the
- -9999 ebuild seems sane since it pulls from git and we don't have to
redist it, but is is possible to RESTRICT="bindist? bindist" ?
Anyone volunteering to tear through this licensing mess and start
breaking things into groups?
- -Zero
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJRJPedAAoJEKXdFCfdEflKhIUQAKXMr8tpwhrFBh2/LxfsdVRQ
n6F72a2KCHyM2YCCQsw3eKskBKmeawQNNKWAQmOaDjn6dcEVi0hxHBLr42m3CZiL
yNA9PRAvRSyshEn8NN/ExTR4eGZft2XqPuhszN129Eu3pJknvKQaPy5ItNzORzN0
FJDherBc2DXs4Uc0VmKxezHxNZZwv1OHIRPtNFGTDy4Eixw4GCYOEg8u1yI23iz7
p+Ef2YjoJPqs9Q3zxuFuJ/is9tIcKdzRy7kNXne92BCvVIst5Dflgg6kQ925eoaM
RifTXv6w1cinItrBRzITftS6j44CcZVpYyRye1ganwuLb90Cxb5U2x8wsj6a1Tcu
okVMWk/ncAHvjrkVoC1/wSpjyCgL5J2EaY5C5O5kkhPxNhwjfICpppawGR7psxAJ
EQjl+u8O6HlVVbPIHTKGlEtSG+HGxVrVX5+CNj39MHEVIhqqVkvw+UenG4lG/Dv8
T+uAjTMYXJzMcVcw90hg8vHmygjXDwIypf0VGf4h+RCloX92dCP5HeBaU79/18Gz
cGfdnOlSsUG7dr+VG4g7O+4AsopNbRe+a2EugGSMQ5IjkK7TaCYFt7K0nKbVYVyt
AeMhsU17/X15rUpYNv37Liu4ythXyldVQMpnvclbx/kwiPR1bK3XSZfvZOX0g5Rb
E2snaN0NNWWCIoj4aK1r
=BJk0
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-02-20 16:19 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 13:08 [gentoo-dev] Packages up for grabs due lack of time Pacho Ramos
2013-02-16 13:38 ` Tom Wijsman
2013-02-16 13:41 ` Aaron Bauman
2013-02-16 13:44 ` Diego Elio Pettenò
2013-02-16 13:59 ` Peter Stuge
2013-02-16 14:00 ` Samuli Suominen
2013-02-16 14:10 ` Diego Elio Pettenò
2013-02-16 15:08 ` Ulrich Mueller
2013-02-16 15:14 ` Rick "Zero_Chaos" Farina
2013-02-16 16:13 ` Ulrich Mueller
2013-02-16 16:28 ` Mike Gilbert
2013-02-16 17:35 ` Ulrich Mueller
2013-02-16 18:40 ` Mike Gilbert
2013-02-16 15:18 ` Diego Elio Pettenò
2013-02-16 15:43 ` Peter Stuge
2013-02-17 17:40 ` Chí-Thanh Christopher Nguyễn
2013-02-18 4:47 ` [gentoo-dev] " Ryan Hill
2013-02-18 11:22 ` Maxim Kammerer
2013-02-18 13:11 ` Chí-Thanh Christopher Nguyễn
2013-02-18 21:02 ` Rémi Cardona
2013-02-16 14:41 ` [gentoo-dev] " Rick "Zero_Chaos" Farina
2013-02-16 14:42 ` Diego Elio Pettenò
2013-02-16 15:11 ` Ulrich Mueller
2013-02-17 5:06 ` Rick "Zero_Chaos" Farina
2013-02-17 10:04 ` [gentoo-dev] linux-firmware (was: Re: Packages up for grabs due lack of time) Ulrich Mueller
2013-02-19 14:18 ` [gentoo-dev] linux-firmware Rick "Zero_Chaos" Farina
2013-02-20 4:43 ` [gentoo-dev] linux-firmware Duncan
2013-02-20 6:03 ` Alec Warner
2013-02-20 7:55 ` Ulrich Mueller
2013-02-20 8:16 ` Alec Warner
2013-02-20 9:09 ` Ulrich Mueller
2013-02-20 16:19 ` Rick "Zero_Chaos" Farina [this message]
2013-02-20 16:44 ` Ulrich Mueller
2013-02-20 16:52 ` Rick "Zero_Chaos" Farina
2013-02-20 8:37 ` Peter Stuge
2013-02-20 12:02 ` Rich Freeman
2013-02-20 12:10 ` Tomáš Chvátal
2013-02-20 13:29 ` Chí-Thanh Christopher Nguyễn
2013-02-20 13:31 ` Diego Elio Pettenò
2013-02-20 13:17 ` Diego Elio Pettenò
2013-02-20 16:03 ` Rich Freeman
2013-02-20 16:10 ` Diego Elio Pettenò
2013-02-20 18:22 ` Greg KH
2013-02-20 18:25 ` Peter Stuge
2013-02-20 18:43 ` Greg KH
2013-02-20 18:51 ` Diego Elio Pettenò
2013-02-21 17:26 ` Greg KH
2013-02-21 17:44 ` Ian Stakenvicius
2013-02-21 18:33 ` Ulrich Mueller
2013-02-21 19:55 ` Greg KH
2013-02-21 20:44 ` Ulrich Mueller
2013-02-21 21:22 ` Rich Freeman
2013-02-21 22:44 ` Greg KH
2013-02-21 23:18 ` Rich Freeman
2013-02-22 1:54 ` David Abbott
2013-02-22 20:53 ` Roy Bamford
2013-02-21 22:16 ` Duncan
2013-02-20 16:28 ` Peter Stuge
2013-02-20 16:37 ` Diego Elio Pettenò
2013-02-20 16:45 ` Alec Warner
2013-02-20 17:01 ` Diego Elio Pettenò
2013-02-20 19:18 ` Chí-Thanh Christopher Nguyễn
2013-02-20 17:17 ` Rich Freeman
2013-02-20 17:25 ` Alec Warner
2013-02-20 17:28 ` Rich Freeman
2013-02-20 17:32 ` Diego Elio Pettenò
2013-02-20 17:42 ` Rich Freeman
2013-02-20 19:20 ` Chí-Thanh Christopher Nguyễn
2013-02-20 19:24 ` Rich Freeman
2013-02-20 19:40 ` Rick "Zero_Chaos" Farina
2013-02-17 10:05 ` [gentoo-dev] Packages up for grabs due lack of time Michał Górny
2013-02-17 10:09 ` Samuli Suominen
2013-02-17 11:42 ` Michał Górny
2013-02-18 5:25 ` [gentoo-dev] " Ryan Hill
2013-02-17 17:35 ` [gentoo-dev] " Chí-Thanh Christopher Nguyễn
2013-02-16 21:45 ` Tim Harder
2013-02-18 10:43 ` Sven Eden
2013-02-18 13:23 ` Anthony G. Basile
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=5124F79D.6010309@gentoo.org \
--to=zerochaos@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