termux-packages/packages/zstd/build.sh

TERMUX_PKG_HOMEPAGE=https://github.com/facebook/zstd
TERMUX_PKG_DESCRIPTION="Zstandard compression."
TERMUX_PKG_LICENSE="GPL-2.0"
TERMUX_PKG_MAINTAINER="@termux"
TERMUX_PKG_VERSION=1.4.9
TERMUX_PKG_REVISION=1
TERMUX_PKG_SRCURL=https://github.com/facebook/zstd/archive/v$TERMUX_PKG_VERSION.tar.gz
TERMUX_PKG_SHA256=acf714d98e3db7b876e5b540cbf6dee298f60eb3c0723104f6d3f065cd60d6a8
TERMUX_PKG_DEPENDS="liblzma, zlib"
TERMUX_PKG_BREAKS="zstd-dev"
TERMUX_PKG_REPLACES="zstd-dev"
TERMUX_PKG_BUILD_IN_SRC=true
new package: zstd (#1786) 2017-11-29 14:48:38 -08:00			`TERMUX_PKG_HOMEPAGE=https://github.com/facebook/zstd`
			`TERMUX_PKG_DESCRIPTION="Zstandard compression."`
add licenses for more packages 2019-01-21 14:53:58 +02:00			`TERMUX_PKG_LICENSE="GPL-2.0"`
explicitly set maintainer for each package In issue https://github.com/termux/termux-packages/issues/6160 I have found that community repo "its-pointless.github.io" specifies us as maintainer for its packages. This is NOT TRUE and potentially misleads people using these packages. Now TERMUX_PKG_MAINTAINER will contain a default value which is neutral and not specify maintainer. So all packages now have to override it to the correct value. [skip ci] %ci:no-build 2020-12-20 15:16:34 +02:00			`TERMUX_PKG_MAINTAINER="@termux"`
zstd: update to 1.4.9 2021-04-01 11:20:08 +01:00			`TERMUX_PKG_VERSION=1.4.9`
zstd: bump revision 2021-04-01 11:41:43 +01:00			`TERMUX_PKG_REVISION=1`
new package: zstd (#1786) 2017-11-29 14:48:38 -08:00			`TERMUX_PKG_SRCURL=https://github.com/facebook/zstd/archive/v$TERMUX_PKG_VERSION.tar.gz`
zstd: update to 1.4.9 2021-04-01 11:20:08 +01:00			`TERMUX_PKG_SHA256=acf714d98e3db7b876e5b540cbf6dee298f60eb3c0723104f6d3f065cd60d6a8`
add zlib to dependencies where needed 2019-04-14 15:51:46 +03:00			`TERMUX_PKG_DEPENDS="liblzma, zlib"`
no more develsplit + provide static libraries as separate package %ci:no-build 2019-07-20 11:42:33 +03:00			`TERMUX_PKG_BREAKS="zstd-dev"`
			`TERMUX_PKG_REPLACES="zstd-dev"`
packages: standardize values of several control variables for build.sh Variables TERMUX_PKG_PLATFORM_INDEPENDENT TERMUX_DEBUG TERMUX_PKG_HAS_DEBUG TERMUX_PKG_ESSENTIAL TERMUX_SUBPKG_ESSENTIAL TERMUX_PKG_NO_STATICSPLIT TERMUX_PKG_BUILD_IN_SRC TERMUX_PKG_FORCE_CMAKE TERMUX_PKG_HOSTBUILD should not accept arbitrary values for marking them "enabled". Instead they should accept boolean values which makes them easier to handle and also makes their meaning clear. build-package.sh should make decision based on variable's value but not on whether it is set or empty. %ci:no-build 2019-08-12 18:28:41 +03:00			`TERMUX_PKG_BUILD_IN_SRC=true`