From: Scott Branden <scott.branden@broadcom.com>
To: Khem Raj <raj.khem@gmail.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org
Cc: Mircea Carausu <mircea.carausu@broadcom.com>
Subject: Re: [PATCH 1/2] common-license: add fdk-aac license file
Date: Tue, 25 Feb 2020 11:38:59 -0800 [thread overview]
Message-ID: <06e06e15-76a8-7c8e-578d-3ac10de79232@broadcom.com> (raw)
In-Reply-To: <90132247-53a6-3ae1-efc0-7aa2479fde86@gmail.com>
On 2020-02-25 11:30 a.m., Khem Raj wrote:
>
> On 2/25/20 11:13 AM, Scott Branden via Openembedded-core wrote:
>> Hi Richard,
>>
>> On 2020-02-25 2:46 a.m., Richard Purdie wrote:
>>> On Mon, 2020-02-24 at 16:11 -0800, Scott Branden via Openembedded-core
>>> wrote:
>>>> From: Mircea Carausu <mircea.carausu@broadcom.com>
>>>>
>>>> Add Fraunhofer FDK AAC Codec Library license.
>>>>
>>>> Signed-offby: Mircea Carausu <mircea.carausu@broadcom.com>
>>>> Signed-off-by: Scott Branden <scott.branden@broadcom.com>
>>> I'm not sure this belongs in Core? Is it a commonly used license? This
>>> recipe isn't in OE-Core? Does the license have an SPDX identifier (I
>>> couldn't see it on https://spdx.org/licenses/)?
>> If we do not add this license the following WARNING is emitted:
>>
>> WARNING: fdk-aac-2.0.1-r0 do_populate_lic: fdk-aac: No generic license
>> file exists for: Fraunhofer_FDK_AAC_Codec_Library_for_Android in any
>> provider
>>
>> We have submitted the fdk-aac recipe to
>> meta-openembedded/meta-multimedia here:
>> https://patchwork.openembedded.org/patch/170495/
>>
>> Please suggest the appropriate place to submit this license.
>> It is an open source license but does not have and SPDX indentifier and
>> is only used for fdk-aac at this time.
> you can propose it for meta-multimedia
That makes more sense. We missed seeing a licenses directory in
meta-multimedia.
>>> Cheers,
>>>
>>> Richard
>>>
>> Thanks,
>> Scott
next prev parent reply other threads:[~2020-02-25 19:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 0:11 [PATCH 1/2] common-license: add fdk-aac license file Scott Branden
2020-02-25 0:11 ` [PATCH 2/2] ffmpeg: add PACKAGECONFIG support for fdk-aac Scott Branden
2020-02-25 10:46 ` [PATCH 1/2] common-license: add fdk-aac license file Richard Purdie
2020-02-25 19:13 ` Scott Branden
2020-02-25 19:28 ` Martin Jansa
2020-02-25 19:30 ` Khem Raj
2020-02-25 19:38 ` Scott Branden [this message]
2020-02-25 19:43 ` Scott Branden
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=06e06e15-76a8-7c8e-578d-3ac10de79232@broadcom.com \
--to=scott.branden@broadcom.com \
--cc=mircea.carausu@broadcom.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=richard.purdie@linuxfoundation.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