Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: OpenEmbedded Core Mailing List
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/4] linux-firmware: Do not deploy license files in packages
Date: Sun, 24 Mar 2013 16:01:39 +0100	[thread overview]
Message-ID: <20130324160139.12fbb4d7@e6520eb> (raw)
In-Reply-To: <1364070660-13157-2-git-send-email-otavio@ossystems.com.br>

Hi Otavio,

Le Sat, 23 Mar 2013 17:30:58 -0300,
Otavio Salvador <otavio@ossystems.com.br> a écrit :
> We don't ship license files with packages and firmware packages are no
> different; drop them.
> 
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>

there may be a good reason to distribute the license files together with
the firmware's binairies : it's often requested by the firmware's
license.

For example in bcm43xx
2.	Restrictions. Licensee shall distribute Software with a copy
of this Agreement. 

Best regards,
Eric



  parent reply	other threads:[~2013-03-24 15:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-23 20:30 [PATCH 1/4] linux-firmware: Use the included Makefile for install Otavio Salvador
2013-03-23 20:30 ` [PATCH 2/4] linux-firmware: Do not deploy license files in packages Otavio Salvador
2013-03-23 21:23   ` Khem Raj
2013-03-23 22:13     ` Otavio Salvador
2013-03-24 15:01   ` Eric Bénard [this message]
2013-03-24 15:42     ` Otavio Salvador
2013-03-24 16:55       ` John Weber
2013-03-24 17:52         ` Eric Bénard
2013-03-23 20:30 ` [PATCH 3/4] linux-firmware: Package vt6656, ath6k, ath9k and ar9170 Otavio Salvador
2013-03-23 20:31 ` [PATCH 4/4] linux-firmware: Add missing license information for wl12xx Otavio Salvador
2013-03-23 21:21 ` [PATCH 1/4] linux-firmware: Use the included Makefile for install Khem Raj
2013-03-23 22:12   ` Otavio Salvador

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=20130324160139.12fbb4d7@e6520eb \
    --to=eric@eukrea.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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