Tue Feb 11 23:25:09 UTC 2020 Eli Schwartz
> "upstream recommends using vendored static linking" is not an acceptable
> reason to violate the packaging guidelines.
>
> The program *must* build using the system versions of the 46
> dependencies listed in the -static package, and the pkgname must be
On 2/10/20 5:02 AM, Felixoid via aur-general wrote:
> Hello, dear TUs and Arch developers.
>
> I'd like to ask relative the package clickhouse-static[1]. The
> officially supported way to build ClickHouse binaries is static
> linking[2]. And my question: is it possible that the package with the
>
On February 10, 2020 5:02:08 AM EST, Felixoid via aur-general
wrote:
> Hello, dear TUs and Arch developers.
>
> I'd like to ask relative the package clickhouse-static[1]. The
> officially supported way to build ClickHouse binaries is static
> linking[2]. And my question: is it possible that the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
It looks like mail-list has added new lines automatically,
so the signature is bad now. Here's the new one.
Best regards,
Mikhail f. Shiryaev
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEESIZn3Pa5datRJo5TOc1XU71dhW8FAl5BS68ACgkQOc1XU71d
hW/8gA/5Ac3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello, dear TUs and Arch developers.
I'd like to ask relative the package clickhouse-static[1]. The
officially supported way to build ClickHouse binaries is static
linking[2]. And my question: is it possible that the package with the
current buildin
