From: Taruntej Kanakamalla <tarun@centricular.com>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Cc: "sebastian@centricular.com" <sebastian@centricular.com>,
"nirbheek@centricular.com" <nirbheek@centricular.com>,
tarun@centricular.com
Subject: Re: [OE-core] [PATCH] gstreamer1.0-plugins-rs: add new package
Date: Wed, 13 May 2026 12:55:08 +0530 [thread overview]
Message-ID: <9aa88cfb4590219b93894806744c6de5bd5b0481.camel@centricular.com> (raw)
In-Reply-To: <DB5PR02MB10213B7E2D21553836D68AAE2EF392@DB5PR02MB10213.eurprd02.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 427 bytes --]
Hi Peter
> AFAICT, there is no splitting of the individual plugins into separate
> packages as is done for the other GStreamer plugin recipes.
> Is this intentional?
Yes, there is no splitting into separate packages in this at the
moment. The gstreamer1.0-plugins-rs is considered as a single package
and it only depends on the PACKAGECONFIG options to include or strip
any particular plugin(s).
Thanks,
Tarun
[-- Attachment #2: Type: text/html, Size: 1141 bytes --]
next prev parent reply other threads:[~2026-05-13 13:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 13:34 [PATCH] gstreamer1.0-plugins-rs: add new package Taruntej Kanakamalla
2026-05-12 10:30 ` [OE-core] " Mathieu Dubois-Briand
2026-05-13 7:14 ` Taruntej Kanakamalla
2026-05-12 19:28 ` Peter Kjellerstedt
2026-05-13 7:25 ` Taruntej Kanakamalla [this message]
2026-05-13 7:56 ` Peter Kjellerstedt
2026-05-13 7:11 ` [PATCH v2] " Taruntej Kanakamalla
2026-05-13 10:19 ` [OE-core] " Alexander Kanavin
2026-05-13 11:23 ` Nirbheek Chauhan
2026-05-13 11:45 ` Alexander Kanavin
2026-05-13 12:02 ` Nirbheek Chauhan
2026-05-13 12:15 ` Alexander Kanavin
2026-05-13 13:10 ` Nirbheek Chauhan
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=9aa88cfb4590219b93894806744c6de5bd5b0481.camel@centricular.com \
--to=tarun@centricular.com \
--cc=nirbheek@centricular.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.com \
--cc=sebastian@centricular.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.