bundled .so libraries (generally unversioned libraries) will be installed.See https://docs.fedoraproject.org/en-US/packaging-guidelines/#_beware_of_rpath
Of which libraries are we talking about? On 24/12/20 14:17, Richard Shaw wrote:
On Thu, Dec 24, 2020 at 1:45 AM Didier Fabert <didier.fabert@xxxxxxxxx <mailto:didier.fabert@xxxxxxxxx>> wrote:Hi, Yes the guidelines are clear for fedora. I miss tell that the package is present in fedora and epel repos and my question is more like this: Is it possible to mix bundled/system libs ? like using system libs (the must part in guidelines) for fedora packages and use bundled one for epel packages (because libs are too old) That's a much more interesting question :)The first line of the main EPEL guidelines[1] says that you must follow the Fedora packaging guidelines and that the EPEL links are for the exceptions for EPEL.So if the library is not available in EPEL, then I would say the answer is yes, you can use the bundled library (even if you're not on Fedora).For the 2nd question, can you use them if the ones in EPEL/RHEL are too old, I'd like to see more feedback from others. Theoretically dependencies in EPEL could be updated, but it has to be done very carefully. For RHEL packages, I tried filling a bug about 6 years ago and as far as I know it's still open, with little to no feedback from RH.
-- --- Antonio Trande Fedora Project mailto: sagitter@xxxxxxxxxxxxxxxxx GPG key: 0x29FBC85D7A51CC2F GPG key server: https://keys.gnupg.net/
Attachment:
OpenPGP_0x29FBC85D7A51CC2F.asc
Description: application/pgp-keys
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature
_______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-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/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx