https://bugzilla.redhat.com/show_bug.cgi?id=1788327 Nicolas Chauvet (kwizart) <kwizart@xxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kwizart@xxxxxxxxx --- Comment #6 from Nicolas Chauvet (kwizart) <kwizart@xxxxxxxxx> --- There is an issue if you have a package that will provides libGL.so.1. Of course that will not be able to override mesa-libGL if already installed (or the libglvnd related package), but it will break compose or even install the wrong libGL.so.1 on i686. The usual way of doing is to exclude the libGL.so.1 from RPM dependency computation. (have a look at libglvnd conditional). Best would be to port this application to libglvnd so it don't have to override libGL.so.1 For information, which use case is behind this package ? I guess you will rely on a proprietary GLES implementation that lacks libGL.so (like some arm devices)? I wonder if this package shouldn't be best in a copr repository... -- 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 _______________________________________________ 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
