package/gitlab-runner: use LIBCURL_FORCE_TLS to enforce TLS support in curl

BR2_PACKAGE_LIBCURL_OPENSSL is part of a "choice" option so it cannot be
selected.  What seems to be really be needed is HTTPS support in curl, so
use the blind LIBCURL_FORCE_TLS option instead (openssl is already
selected).

Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
This commit is contained in:
Peter Korsgaard 2023-02-06 15:59:29 +01:00
parent 71c1324940
commit b95f7591bd

View File

@ -11,7 +11,7 @@ config BR2_PACKAGE_GITLAB_RUNNER
select BR2_PACKAGE_GIT # runtime select BR2_PACKAGE_GIT # runtime
select BR2_PACKAGE_LIBCURL # runtime select BR2_PACKAGE_LIBCURL # runtime
select BR2_PACKAGE_LIBCURL_CURL # runtime select BR2_PACKAGE_LIBCURL_CURL # runtime
select BR2_PACKAGE_LIBCURL_OPENSSL # runtime, for ca-certificates. select BR2_PACKAGE_LIBCURL_FORCE_TLS # runtime
select BR2_PACKAGE_OPENSSL # runtime select BR2_PACKAGE_OPENSSL # runtime
select BR2_PACKAGE_OPENSSL_FORCE_LIBOPENSSL # runtime select BR2_PACKAGE_OPENSSL_FORCE_LIBOPENSSL # runtime
select BR2_PACKAGE_LIBOPENSSL_BIN # runtime select BR2_PACKAGE_LIBOPENSSL_BIN # runtime