https://bugzilla.redhat.com/show_bug.cgi?id=960201 --- Comment #18 from Michael Schwendt <bugs.michael@xxxxxxx> --- > By e.g. adding /etc/ldconf.so.conf.d/libyui-%{%_arch}.conf to the libyui-pkg That's making available private _plugin_ libs (as dlopen'ed by libyui) in runtime linker's search path. I don't understand what that's supposed to fix. Why store the plugins in a private subdir first of all? > because the other UI-plugins are affected by this as well. Hmmmmm… Who did > the review on them? :-P Haha, -devel packages for an API that may be used to extend _plugin_ libs scare me and cause quite a headache, too (guess why I've lobbied for the longer -devel packaging guidelines related to placement of .so files) . How much to examine beyond a plausibility-check (based on what %description claims)? Reviewing such packages would be easier, if there were an API-user that would extend a plugin and could be tested with. It wouldn't be the first time such headers won't be used. And there have been enough cases where the headers were private and were installed accidentally (e.g. suspicious header-only -devel packages for plugin libs). If you are concerned about the automatic SONAME deps of the individual plugin libs, while one common option would be to filter them out, this would get really funny with the introduction of an extension plugin lib depending on a plugin lib. This is non-trivial stuff. -- 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 https://admin.fedoraproject.org/mailman/listinfo/package-review