https://bugzilla.redhat.com/show_bug.cgi?id=1942132 --- Comment #64 from Nicolas Chauvet (kwizart) <kwizart@xxxxxxxxx> --- (In reply to František Zatloukal from comment #63) > (In reply to Nicolas Chauvet (kwizart) from comment #62) > > libigfxcmrt is still built as a separate shared object, but as such, this is > > a dead project: https://github.com/intel/cmrt > > > > Please remove this sub-package unless you can point to any users ? > > I mean, I don't have any preference here, but what's the harm if it's in a > subpackage and built by default? In my opinion, we can remove it once > upstream at least starts not to build it by default? End-users will have to swap to the full intel-media-driver by hands. Having this package might interfere with this process. I don't get what you mean by "once it's upstream" ? There is no plan to get this library into a separate project. This is backward. cmrt is now part of intel-media-driver and not meant as separate library. > > Also according to version numbers in 23.4 is pre-release software (might > > need any ABI breaking update). please only import in rawhide for now. > > > Yeah, I always forget that tags are just for development versions here, will > keep that in mind once it's imported and follow stable releases unless we > need to use devel for some reason. Thanks > On the other hand, I don't see a big harm in importing it to f39 too? The > API/ABI should be "libva/VAAPI" no? And if there arrives something that > depends on the distributed .so (can/should that happen?), we can handle that > in a side-tag? What I mean by 23.4 is pre-release is that any later 23.4 serie can mandates any higher libva library (or else) than what currently has f39. Also Intel VAAPI is know to silent break ABI from time to time, so even minor releases need to be carefully audited. At the end, we don't want to rebuild all libva userspace deps for a single driver update (even if we could do this in fedora/rpmfusion it will nevertheless break many legitimate copr users that might have different maintenance pace). I hope to have clarified the point. -- You are receiving this mail because: You are always notified about changes to this product and component You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=1942132 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%201942132%23c64 -- _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
