public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Non-free software in Gentoo
Date: Wed, 6 Jan 2010 10:57:25 -0800	[thread overview]
Message-ID: <20100106185725.GA4033@kroah.com> (raw)
In-Reply-To: <4B4417D5.3050403@doublecreations.com>

On Tue, Jan 05, 2010 at 11:55:49PM -0500, Vincent Launchbury wrote:
> Greg KH wrote:
> > And note, _I_ placed those images in the kernel image, after consulting
> > lawyers about this issue, so it's not like I don't know what I am
> > talking about here.
> 
> I'm not questioning whether it's legal to distribute non-free firmware
> alongside the GPL. I'm merely saying that the firmware _is_ non-free,
> which should be reflected by the ebuild licenses.

So you are saying that the license for the kernel should show the
license for all of the different firmware files as well?  That would get
pretty unusable, and keep the kernel from being able to be installed on
anyone's machine that didn't want such licenses, right?

Also note that the license of the firmware files do not matter to almost
everyone using the kernel, as almost no one uses those files anymore,
the ones in the linux-firmware package should be used instead.

So as we are a source-based distro, if you object to those firmware
licenses, just don't build them in your kernel builds.  But to expect to
list all of them as the license for the whole kernel package, that's not
a workable solution as far as I can see.

> > So it's a pointless effort.
> 
> To you maybe, but it's important to some. Note that updating the
> licenses would only affect those with strict ACCEPT_LICENSE settings
> anyway. I don't understand why you'd oppose the change.

So you want anyone with such strict settings to not be able to install
the kernel package at all?  If so, what kernel do you want them to be
able to use?  :)

thanks,

greg k-h



  reply	other threads:[~2010-01-06 20:18 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-28  5:36 [gentoo-dev] Non-free software in Gentoo Vincent Launchbury
2009-12-28  8:10 ` Rémi Cardona
2009-12-28 13:11   ` Nirbheek Chauhan
2009-12-29  8:59     ` Peter Volkov
2009-12-29  5:24   ` Vincent Launchbury
2009-12-29  9:02     ` Peter Volkov
2009-12-29 18:32       ` Robin H. Johnson
2009-12-29 23:17         ` Brian Harring
2009-12-28 11:21 ` Jeroen Roovers
2009-12-28 14:37 ` Jeremy Olexa
2009-12-28 18:56 ` Robin H. Johnson
2009-12-28 22:15   ` Richard Freeman
2009-12-28 22:53     ` Robin H. Johnson
2009-12-29  1:16       ` Richard Freeman
2009-12-30  0:52         ` Greg KH
2009-12-30 11:43           ` Richard Freeman
2009-12-31  4:51             ` Greg KH
2009-12-31  6:02               ` Harald van Dijk
2009-12-30  0:50 ` Greg KH
2009-12-30  2:42   ` Vincent Launchbury
2009-12-31  4:48     ` Greg KH
2009-12-31 12:30       ` Richard Freeman
2010-01-06  4:55       ` Vincent Launchbury
2010-01-06 18:57         ` Greg KH [this message]
2010-01-06 21:55           ` Harald van Dijk
2010-01-07  6:19             ` Vincent Launchbury
2010-01-07 14:37               ` Richard Freeman
2010-01-08  5:26               ` Greg KH
2010-01-08 15:48                 ` Richard Freeman

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=20100106185725.GA4033@kroah.com \
    --to=gregkh@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