From: Richard Braun <rbraun@sceen.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pkg-infra: produce legal info for proprietary packages
Date: Tue, 16 Oct 2012 17:42:29 +0200 [thread overview]
Message-ID: <20121016154229.GA15417@mail.sceen.net> (raw)
In-Reply-To: <506AEF12.5080906@lucaceresoli.net>
On Tue, Oct 02, 2012 at 03:41:38PM +0200, Luca Ceresoli wrote:
> intel-microcode is clearly not fitting any of the two categories: we want to
> describe its license, but we are not allowed to redistribute it freely, as
> the license text reported from Richard seems to signify.
Actually, there is a license text embedded in the microcode file. It
reads :
Redistribution. Redistribution and use in binary form, without modification, are
permitted provided that the following conditions are met:
.Redistributions must reproduce the above copyright notice and the following
disclaimer in the documentation and/or other materials provided with the
distribution.
.Neither the name of Intel Corporation nor the names of its suppliers may be used
to endorse or promote products derived from this software without specific prior
written permission.
.No reverse engineering, decompilation, or disassembly of this software is
permitted.
."Binary form" includes any format commonly used for electronic conveyance
which is a reversible, bit-exact translation of binary representation to ASCII or
ISO text, for example, "uuencode."
The disclaimer is a common 'this software is distributed "as is"'
notice.
I'm not exactly sure what "redistribute it freely" means here, since I'm
much more used to free licenses, but it seems to me that redistribution
is actually allowed as buildroot isn't in any way violating any of these
conditions, as long as this text appears in the list of licenses, which
my patch takes care of.
Do you agree with that, and if yes, how would that change the rework
proposal ?
--
Richard Braun
next prev parent reply other threads:[~2012-10-16 15:42 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
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 [this message]
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=20121016154229.GA15417@mail.sceen.net \
--to=rbraun@sceen.net \
--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