https://bugzilla.redhat.com/show_bug.cgi?id=1415143 --- Comment #4 from Hans de Goede <hdegoede@xxxxxxxxxx> --- About the email discussion about the etc/egl/egl_external_platform.d and /usr/share/egl/egl_external_platform.d directories and dropping a json file there so that eglexternalplatform can actually find egl-wayland (if I've understood things correctly): I'm going to need some info on how all these new bits fit together. So egl-wayland is a (the wayland) platform provider for eglexternalplatform right? Then it should also runtime depend on eglexternalplatform, either through auto .so.x dependencies, or explicit in the spec I assume ? Then to me it would make sense for the main eglexternalplatform pkg to create/own the /etc/egl/egl_external_platform.d and /usr/share/egl/egl_external_platform.d directories. I agree that if eglexternalplatform finds its platform providers / plugins through json files, that the json file should be part of the package which contains the .so file which contains the platform-provider implementation, so in this specific case the main egl-wayland package. About the egl-wayland package, I don't think it make sense to have a -devel there as there are no headers and this is a plugin, depending on how the json to load it refers to the .so, either drop the .so symlink or if it is necessary make it part of the main pkg and add a comment to the %files section why it is there. -- 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