From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pkg-infra: produce legal info for proprietary packages
Date: Fri, 28 Sep 2012 19:05:26 +0200 [thread overview]
Message-ID: <20120928190526.79db5cde@skate> (raw)
In-Reply-To: <CAAXf6LUF1bOSTGyMtC2OEbQSOeDiMphktpxtSZHmLj4ms9c+yQ@mail.gmail.com>
Thomas,
On Fri, 28 Sep 2012 18:40:04 +0200, Thomas De Schampheleire wrote:
> Additionally, it would be nice to get some context. Why do you need this?
> What its the use case?
>
> The proprietary packages are not in the current legal info, precisely
> because you wouldn't distribute them.
> If you have a package that you distribute under a non open-source license,
> I think it makes more sense to provide a real name to the license.
There are things like firmware, or DSP blobs or other stuff that are
just provided in binary form, but their license allows free
redistribution. Should we mark those as PROPRIETARY, or should we have
a different license name for those?
Basically, the context is the intel-microcode package, which bundles a
binary-only firmware for some Intel hardware. Which license
informations should we attach to it?
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-09-28 17:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 15:12 [Buildroot] [PATCH] intel-microcode: new package Richard Braun
2012-09-20 20:36 ` Thomas Petazzoni
2012-09-20 21:12 ` Richard Braun
2012-09-21 8:35 ` Thomas Petazzoni
2012-09-22 9:42 ` Richard Braun
2012-09-28 12:17 ` Richard Braun
2012-09-28 12:20 ` [Buildroot] [PATCH] pkg-infra: produce legal info for proprietary packages Richard Braun
2012-09-28 12:23 ` Thomas Petazzoni
2012-09-28 16:40 ` Thomas De Schampheleire
2012-09-28 17:05 ` Thomas Petazzoni [this message]
2012-09-28 18:52 ` Thomas De Schampheleire
2012-09-30 14:22 ` Arnout Vandecappelle
2012-10-02 13:41 ` Luca Ceresoli
2012-10-02 14:35 ` Arnout Vandecappelle
2012-10-02 17:50 ` Thomas De Schampheleire
2012-10-16 15:42 ` Richard Braun
2012-10-20 20:51 ` Luca Ceresoli
2012-10-20 21:55 ` Richard Braun
2012-09-28 12:20 ` [Buildroot] [PATCH] intel-microcode: new package Richard Braun
2012-09-28 12:24 ` Thomas Petazzoni
2012-09-29 9:31 ` Thomas De Schampheleire
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=20120928190526.79db5cde@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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