From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: curl: restore libcurl-gnutls symlink from libcurl.
Date: Sun, 17 Jul 2022 21:28:57 +0200 [thread overview]
Message-ID: <20220717192857.mic5lWBsEs8zXXuQ1Jy_RF9ofrvNA354NMkeKvZ2BOY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36619@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/36619#issuecomment-1186593922
Comment:
> You can't just create a soname to a incompatible library version and even worse, make the build system using it (setting bogus shlib_provides). this is not improving Void in any form, just making it broken (therefore used "bogus" to describe that)
It's not incompatible. The issue is Debian doing Debian things and naming their libcurl after the TLS library used to build it, for whatever license compatibility reason. The libcurl API/ABI is the same across the library versions.
We removed the workaround from the curl package because that felt like the wrong place for it; it's not really our place to provide this fix.
> I was thinking about asking the support to create a "static" version of their plugins, this should be sufficient to run it everywhere, even on Void.
How would that work? If plugins are dlopened, linking them as statically as possible can be complicated business.
next prev parent reply other threads:[~2022-07-17 19:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 17:56 [PR PATCH] " prez
2022-04-11 17:13 ` leahneukirchen
2022-04-11 17:32 ` prez
2022-06-17 16:47 ` fdziarmagowski
2022-06-17 18:16 ` prez
2022-06-17 20:16 ` fdziarmagowski
2022-06-17 22:32 ` prez
2022-07-17 19:28 ` ericonr [this message]
2022-07-20 20:48 ` fdziarmagowski
2022-10-19 2:14 ` github-actions
2022-10-19 4:30 ` biopsin
2023-01-19 2:00 ` github-actions
2023-02-02 2:01 ` [PR PATCH] [Closed]: " github-actions
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220717192857.mic5lWBsEs8zXXuQ1Jy_RF9ofrvNA354NMkeKvZ2BOY@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).