Buy commercial curl support. We
help you work out your issues, debug your libcurl applications, use the API,
port to new platforms, add new features and more. With a team lead by the
curl founder Daniel himself.
Re: How to package wcurl with curl 8.14.0
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: gromit via curl-distros <curl-distros_at_lists.haxx.se>
Date: Sun, 25 May 2025 00:45:32 +0200
On 25/05/24 09:28PM, Samuel Henrique via curl-distros wrote:
> Hello everyone,
Hey Samuel,
> Me and fossdd had a brief conversation in the curl IRC/Matrix channel about
> distros who ship wcurl as its own package and what to do starting with curl
> 8.14.0.
>
> My strong recommendation is to let wcurl be installed as part of the curl
> package. The convenience of wcurl is its strongest value, and having it shipped
> as a separate package will diminish that.
>
> So what to do if you're a distribution which already shipped wcurl as its own
> package?
>
> If you agree with following upstream and installing wcurl on the curl
> package (starting on 8.14.0), you have a few options depending on how you
> handle the now-deprecated wcurl package, here are two suggestions:
>
> 1) Turn the wcurl package into an empty (transitional) package which only
> depends on the curl package.
>
> 2) Just remove the wcurl package from your repositories, users who installed it
> are guaranteed to have the curl package since it was a dependency.
>
> Depending on how package relationships work in your environment, you can also
> declare a conflict to wcurl in the curl package, this would help ensure the
> wcurl package is dropped in user's systems once they install curl > 8.14.0.
I have already prepared this in Arch Linux:
https://gitlab.archlinux.org/archlinux/packaging/packages/curl/-/merge_requests/6
> Regards,
A bit sad to lose wcurl from my list of maintained packages, but I know
it will be in good hands with the curl packagers ;)
Cheers,
Chris
Received on 2025-05-25
Date: Sun, 25 May 2025 00:45:32 +0200
On 25/05/24 09:28PM, Samuel Henrique via curl-distros wrote:
> Hello everyone,
Hey Samuel,
> Me and fossdd had a brief conversation in the curl IRC/Matrix channel about
> distros who ship wcurl as its own package and what to do starting with curl
> 8.14.0.
>
> My strong recommendation is to let wcurl be installed as part of the curl
> package. The convenience of wcurl is its strongest value, and having it shipped
> as a separate package will diminish that.
>
> So what to do if you're a distribution which already shipped wcurl as its own
> package?
>
> If you agree with following upstream and installing wcurl on the curl
> package (starting on 8.14.0), you have a few options depending on how you
> handle the now-deprecated wcurl package, here are two suggestions:
>
> 1) Turn the wcurl package into an empty (transitional) package which only
> depends on the curl package.
>
> 2) Just remove the wcurl package from your repositories, users who installed it
> are guaranteed to have the curl package since it was a dependency.
>
> Depending on how package relationships work in your environment, you can also
> declare a conflict to wcurl in the curl package, this would help ensure the
> wcurl package is dropped in user's systems once they install curl > 8.14.0.
I have already prepared this in Arch Linux:
https://gitlab.archlinux.org/archlinux/packaging/packages/curl/-/merge_requests/6
> Regards,
A bit sad to lose wcurl from my list of maintained packages, but I know
it will be in good hands with the curl packagers ;)
Cheers,
Chris
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-distros Etiquette: https://curl.se/mail/etiquette.html
- application/pgp-signature attachment: signature.asc