From: zlice <zlice@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New Intel packages v2
Date: Tue, 21 Nov 2023 00:03:52 +0100 [thread overview]
Message-ID: <20231120230352.N2vEtkEPkgfLfhVUy4xZv8FH7e5JAtZn-prayehSi1A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47330@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
There's a closed pull request on the void-packages repository
New Intel packages v2
https://github.com/void-linux/void-packages/pull/47330
Description:
#### Testing the changes
- I tested the changes in this PR: **YES**
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**
#### Local build testing
- I built this PR locally for my native architecture, **x86_64**
#### Comments
https://github.com/void-linux/void-packages/pull/41132 was coming up on a year but got closed while dealing with github account lockout and other stuff.
Packages prep for Intel DG2/Alchemist/Arc codec support for ffmpeg6.
OneVPL is the successor to IntelMediaSDK (libmfx), but only one of these can be enabled in ffmpeg. Removed ffmpeg (4) changes so these packages touch nothing and are only for https://github.com/void-linux/void-packages/pull/43761.
- onevpl (replaces intel-media-sdk - but only available in ffmpeg 6)
- onevpl-intel-gpu
- intel-media-sdk
- libmfx (part of intel-media-sdk)
next prev parent reply other threads:[~2023-11-20 23:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 22:42 [PR PATCH] " zlice
2023-11-20 23:03 ` zlice [this message]
2023-11-20 23:03 ` zlice
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=20231120230352.N2vEtkEPkgfLfhVUy4xZv8FH7e5JAtZn-prayehSi1A@z \
--to=zlice@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).