From: "Eric Bénard" <eric@eukrea.com>
To: John Weber <rjohnweber@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/4] linux-firmware: Do not deploy license files in packages
Date: Sun, 24 Mar 2013 18:52:31 +0100 [thread overview]
Message-ID: <20130324185231.4ed1f60b@e6520eb> (raw)
In-Reply-To: <514F2FED.70603@gmail.com>
Le Sun, 24 Mar 2013 11:55:09 -0500,
John Weber <rjohnweber@gmail.com> a écrit :
> Showing my ignorance here, but is a manifest created with all of the packaged
> licenses? Is it possible for the developer to ship that if they see fit?
>
> I think what Otavio was trying to do was to keep /lib/firmware from being
> cluttered with license files. At least, that is the benefit as I see it.
>
I see the benefit, I was just giving a reason why the initial recipe
writer may have wanted to include the license files in the packages
together with the binaries of the firmwares.
Eric
next prev parent reply other threads:[~2013-03-24 18:10 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
2013-03-24 15:42 ` Otavio Salvador
2013-03-24 16:55 ` John Weber
2013-03-24 17:52 ` Eric Bénard [this message]
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=20130324185231.4ed1f60b@e6520eb \
--to=eric@eukrea.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rjohnweber@gmail.com \
/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