From: Markus Volk <f_l_k@t-online.de>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [oe-core][PATCH 1/2] introduce virtual/ffmpeg
Date: Sat, 20 Sep 2025 13:02:28 +0200 [thread overview]
Message-ID: <40WV2T.MJDR58EBBGYO@t-online.de> (raw)
In-Reply-To: <1866F8043523DE78.12551@lists.openembedded.org>
[-- Attachment #1: Type: text/plain, Size: 909 bytes --]
But that's only because I had to think about it again. I totally
understand your point.
On Sat, Sep 20 2025 at 12:49:50 +02:00:00, Markus Volk via
lists.openembedded.org <f_l_k=t-online.de@lists.openembedded.org> wrote:
> On Tue, Sep 16 2025 at 18:26:32 +02:00:00, Alexander Kanavin
> <alex.kanavin@gmail.com> wrote:
>> This needs more detail. What else would be providing virtual/ffmpeg,
>> other than ffmpeg itself? Why the justification is talking about
>> 'different versions', and not different providers?
>
>
> Because it's been a while, I found it surprisingly difficult to get
> to the point ;)
>
> I think I tried it as you recommended, and I also think that I only
> needed virtual/kodi at the time.
> The 'idea' of virtual/ffmpeg is introduced in meta-raspberrypi
> because it provides rpidistro-ffmpeg,
> and the build system therefore expects me to set a PREFERRED_PROVIDER
> for it.
[-- Attachment #2: Type: text/html, Size: 1243 bytes --]
prev parent reply other threads:[~2025-09-20 11:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 15:57 [oe-core][PATCH 1/2] introduce virtual/ffmpeg Markus Volk
2025-09-16 15:58 ` [oe-core][PATCH 2/2] gstreamer1.0-libav: depend on virtual/ffmpeg Markus Volk
2025-09-16 16:04 ` Patchtest results for [oe-core][PATCH 1/2] introduce virtual/ffmpeg patchtest
2025-09-16 16:26 ` Alexander Kanavin
2025-09-16 16:51 ` Markus Volk
[not found] ` <1865D16D5AB1B07F.13540@lists.openembedded.org>
2025-09-16 17:06 ` Markus Volk
2025-09-16 19:14 ` Alexander Kanavin
2025-09-20 10:49 ` Markus Volk
[not found] ` <1866F8043523DE78.12551@lists.openembedded.org>
2025-09-20 11:02 ` Markus Volk [this message]
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=40WV2T.MJDR58EBBGYO@t-online.de \
--to=f_l_k@t-online.de \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.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 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.