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: Tue, 16 Sep 2025 18:51:29 +0200 [thread overview]
Message-ID: <THXO2T.ZRRK3LJE5VX61@t-online.de> (raw)
In-Reply-To: <CANNYZj964ZPDbN7HjhCCkxS5a9dPR7-uVewK9pcrpcZp9ZVGLw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
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?
I was talking about versions, because thats what I use it for. A
different provider would be e.g libav,but in meta-kodi I have older
versions of ffmpeg
called ffmpeg-6 and ffmpeg-7 and let them provide virtual/ffmpeg. Dont
ask me why I didn't stick with
preferred_version. I only remember that I had issues with using it but
not exactly what it was. But if you think this
is the way it should be, I can give it another try
[-- Attachment #2: Type: text/html, Size: 921 bytes --]
next prev parent reply other threads:[~2025-09-16 16:51 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 [this message]
[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
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=THXO2T.ZRRK3LJE5VX61@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.