On Oct 29, 2017 9:11 AM, "Bruce Dubbs" <[email protected]> wrote:
Armin K. wrote: > On 29.10.2017 2:24, Bruce Dubbs wrote: > >> Armin K. wrote: >> >>> On 29.10.2017 1:28, via blfs-book wrote: >>> >>>> Author: bdubbs >>>> Date: Sat Oct 28 16:28:23 2017 >>>> New Revision: 19406 >>>> >>>> Log: >>>> Update to intel-vaapi-driver and libva 2.0.0, >>>> but gstreamer-vaapi-1.12.3 is broken until the next >>>> gstreamer release. >>>> >>>> >>> I'm pretty sure this was a good reason NOT to update, no? >>> >> >> Can always revert if gstreamer does not do a release. gstreamer-vaapi >> is an end-program and optimization at that. Nothing depends on it and >> all the other packages that use libva are ok. >> > You could argue that anything that uses gstreamer for playing video uses > gst-vaapi. It adds hardware accelerated paths for several codecs on video > hardware that supports it. > > Same way, neither gst-plugins-ugly nor gst-libav have anything dependent > on them, but you can't use some apps relying on gstreamer for playing > certain media if you don't have them installed. > > And since libva 2.0.0 is a big bump, gst-vaapi won't support it until next > minor version (1.14), and there's no sight of that one yet. > I see your point. I'll think about reverting. Historically, it looks like gst* makes a release about every two months and it's been six weeks since the last one. I did check every package that mentions libva and gstreamer-vaapi was the only one that complained. I don't understand the problem. They all built fine for me.
-- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
