All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Volk <f_l_k@t-online.de>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: RE: [oe] [meta-multimedia][PATCHv7] pipewire: update to v0.3.56
Date: Sun, 21 Aug 2022 16:01:25 +0200	[thread overview]
Message-ID: <DMXYGR.GU3KE5WIU42D1@t-online.de> (raw)
In-Reply-To: <52f6ee030dbf4e88a86e3702a5303d57@axis.com>

[-- Attachment #1: Type: text/plain, Size: 726 bytes --]


i tried to follow your suggestions,
Thanks

Am So, 21. Aug 2022 um 12:49:24 +0000 schrieb Peter Kjellerstedt 
<peter.kjellerstedt@axis.com>:
> AFAIK, there are no current examples of "gstreamer" being used a
> distro feature. What is it supposed to mean? When is it supposed to
> be used? Why is it needed?


I found an example of this, but I must confess that this was in an old 
third-party layer. What I want this DISTRO_FEATURE for is the ability 
to use it to enable/disable gstreamer support in recipes. Not just here 
in pipewire. The same goes for Jack. Is this already used as a 
DISTRO_FEATURE? If so, maybe we could use it to make the Jack server 
depend on it instead of always building it as it currently does?


[-- Attachment #2: Type: text/html, Size: 970 bytes --]

  reply	other threads:[~2022-08-21 14:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-20 19:11 [meta-multimedia][PATCHv7] pipewire: update to v0.3.56 Markus Volk
2022-08-20 19:13 ` Markus Volk
2022-08-21 12:49 ` [oe] " Peter Kjellerstedt
2022-08-21 14:01   ` Markus Volk [this message]
2022-08-22  8:35     ` Peter Kjellerstedt
2022-08-22 14:14       ` Khem Raj
2022-08-22 15:48         ` Markus Volk
     [not found]         ` <170DB56ADBD007D9.17953@lists.openembedded.org>
2022-08-22 17:18           ` Markus Volk

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=DMXYGR.GU3KE5WIU42D1@t-online.de \
    --to=f_l_k@t-online.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=peter.kjellerstedt@axis.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.