All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: afd@ti.com
Cc: Denys Dmytriyenko <denys@konsulko.com>,
	Ryan Eatmon <reatmon@ti.com>,
	meta-arago@lists.yoctoproject.org
Subject: Re: [meta-arago][scarthgap/master][PATCH v2 6/7] arago.conf: Remove unneeded LICENSE_FLAGS_ACCEPTED items
Date: Wed, 22 Jan 2025 17:24:01 -0500	[thread overview]
Message-ID: <20250122222401.GS21836@denix.org> (raw)
In-Reply-To: <20250121175231.27183-6-afd@ti.com>

On Tue, Jan 21, 2025 at 11:52:30AM -0600, Andrew Davis via lists.yoctoproject.org wrote:
> netperf is no longer marked as non-commercial (587fe5877 in meta-oe).
> 
> faad2 is still marked commercial and AAC is still covered under several
> patents that may require royalties. Not sure why we decided to whitelist
> this, the commit adding it has no message. So, what can be added without
> explanation can be removed without explanation :)

Heh... IIRC, there was an unconditional build dependency back then, probably a 
mistake. If removing it doesn't break anything, then it should be removed.


> gst-ffmpeg is no longer a package, remove this too.
> 
> Signed-off-by: Andrew Davis <afd@ti.com>
> ---
> 
> Changes for v2:
>  - Explain each change better in commit message
> 
>  meta-arago-distro/conf/distro/arago.conf | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta-arago-distro/conf/distro/arago.conf b/meta-arago-distro/conf/distro/arago.conf
> index 9f51ac26..033b8fcd 100644
> --- a/meta-arago-distro/conf/distro/arago.conf
> +++ b/meta-arago-distro/conf/distro/arago.conf
> @@ -167,7 +167,7 @@ SKIP_META_VIRT_SANITY_CHECK = "1"
>  # disable by default the codecs in libav that causes issues with shipping an
>  # Arago based SDK. No need to prevent gst-ffmpeg from being used since we
>  # disable troublesome software.
> -LICENSE_FLAGS_ACCEPTED = "commercial_gst-ffmpeg commercial_gstreamer1.0-libav commercial_faad2 non-commercial_netperf"
> +LICENSE_FLAGS_ACCEPTED = "commercial_gstreamer1.0-libav"
>  
>  # Do not package own copy of perl into devkit, rely on host one
>  ASSUME_PROVIDED += "nativesdk-perl"
> -- 
> 2.39.2


  reply	other threads:[~2025-01-22 22:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-21 17:52 [meta-arago][scarthgap/master][PATCH v2 1/7] arago.conf: Remove old and unused config flags Andrew Davis
2025-01-21 17:52 ` [meta-arago][scarthgap/master][PATCH v2 2/7] arago.conf: Remove leftover comments around security protections Andrew Davis
2025-01-21 17:52 ` [meta-arago][scarthgap/master][PATCH v2 3/7] arago-prefs.inc: Remove PREFERRED_PROVIDER for jpeg Andrew Davis
2025-01-21 17:52 ` [meta-arago][scarthgap/master][PATCH v2 4/7] opencv: Remove OpenCV customization and DISTRO_FEATURE Andrew Davis
2025-01-21 17:52 ` [meta-arago][scarthgap/master][PATCH v2 5/7] arago.conf: Remove OpenMP as a DISTRO_FEATURE Andrew Davis
2025-01-21 17:52 ` [meta-arago][scarthgap/master][PATCH v2 6/7] arago.conf: Remove unneeded LICENSE_FLAGS_ACCEPTED items Andrew Davis
2025-01-22 22:24   ` Denys Dmytriyenko [this message]
2025-01-21 17:52 ` [meta-arago][scarthgap/master][PATCH v2 7/7] ffmpeg: Remove bbappend to disable x264 Andrew Davis

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=20250122222401.GS21836@denix.org \
    --to=denis@denix.org \
    --cc=afd@ti.com \
    --cc=denys@konsulko.com \
    --cc=meta-arago@lists.yoctoproject.org \
    --cc=reatmon@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.