Issues with PKGBUILD

[dvzrv]

Hi!

I would like to point out a few issues with the PKGBUILD, as I became aware of this project via the cURL developer Daniel Stenberg (https://chaos.social/@bagder@mastodon.social/110094392014179398).

Please make sure to follow the Arch Package guidelines for your PKGBUILD, more specifically those interacting with version control systems. In its current state the PKGBUILD is unfortunately a recipe for disaster, as users would end up in unclear system states (curl components of differing origin installed on the same system, disregarding the sonames of libcurl.so).

TL;DR:

• Your PKGBUILD should not be creating packages called curl, libcurl-compat and libcurl-gnutls as they conflict with the official core/curl.
• The packages created from your PKGBUILD should conflict with and provide curl, libcurl-compat and libcurl-gnutls (respectively) and must depend on the specific version of curl that you provide
• The pkgrel variable should not be used this way (see https://wiki.archlinux.org/title/PKGBUILD#pkgrel for details)
• Use a pkgver() function to create a specific version string (see https://wiki.archlinux.org/title/PKGBUILD#pkgver for details)

There is the AUR package curl-git which does more or less what you intend to do with this repository (minus adding a specific date timestamp). Updating/Building that PKGBUILD daily and pushing it to an unofficial user repository would be the preferred/ canonical way.

Please be aware that providing a core component such as curl (which is relied upon by many other packages) has breaking potential (e.g. when a soname change occurs and the dependent packages have not been rebuilt against the new version of curl).

[pheiduck]

Hey,

Thanks for your note, you are welcome to create a PR to submit the changes accordingly. And this PKG is for development and should not be used on production Environments or things like that.