https://bugzilla.redhat.com/show_bug.cgi?id=1942132
--- Comment #37 from František Zatloukal <fzatlouk(a)redhat.com> ---
(In reply to Nicolas Chauvet (kwizart) from comment #36)
I don't get why there is a libigfxcmrt sub-package out of this
project. Is
this used by some other component ?
My understanding is that library is a fork of this project:
https://koji.fedoraproject.org/koji/buildinfo?buildID=2114125
It seems like (eg.
https://packages.debian.org/unstable/libigfxcmrt-dev ;
https://packages.ubuntu.com/search?keywords=libigfxcmrt-dev ).
Now if intel-media-driver is the only user of the library, I don't get the
problem to have it bundled at all.
It will avoid the need of any ABI computation.
That'd be the case, but media-driver isn't the user of the library, this
library depends on media-driver (and something else can depend on this lib).
I'd say there is no point in having it as a part of intel-media-driver
directly, and (the other option) waste to just rm that file (and the entire
libigfxcmrt-devel) I guess since it gets compiled anyway?
Also it will ease the swap between the full featured and
I wouldn't say many users would install this library, and if this ever gets to
Fedora, we can add something like Requires: intel-media-driver-free or
intel-media-driver to it.
Until a solution is found WRT alternative version
(
https://github.com/intel/libva/issues/639 ), I would be okay to have a
downstream patch with the iHD-free driver name added into libva.
Please rename as appropriate.
Okay, I'll keep that in mind, thanks (this is nowhere near legal ack yet
afaik)!
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
https://bugzilla.redhat.com/show_bug.cgi?id=1942132