Re: bundled libraries

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

It's for netdata package and specifically for the cloud registration feature. So netdata is working fine without this feature but a lot of users claim this feature.

All bundled libs are static, so there is no additional .so file installed (neither fedora nor epel repos).

We're talking about libwebsockets (min 3.2.2 and epel provides 3.0.1) and a "patched" version of mosquitto

For fedora package, it's working with libwebsockets from system, but not mosquitto.

For epel, I have to use bundled libs (for both) otherwise, it's not working.

Best Regards,

Didier FABERT.

Le 24/12/2020 à 15:01, Antonio T. sagitter a écrit :
Bundled libraries are permitted as long as they do not conflict with system libraries. In your case, it does not happen in Fedora but in EPEL it does; so i would advice you to use a private lib directory in EPEL where
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.




_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 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/devel@xxxxxxxxxxxxxxxxxxxxxxx

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 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/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux