termux-packages/packages/libmsgpack/build.sh

TERMUX_PKG_HOMEPAGE=https://github.com/msgpack/msgpack-c/
TERMUX_PKG_DESCRIPTION="MessagePack implementation for C"
TERMUX_PKG_LICENSE="Apache-2.0"
TERMUX_PKG_MAINTAINER="@termux"
TERMUX_PKG_VERSION=4.0.0
TERMUX_PKG_SRCURL=https://github.com/msgpack/msgpack-c/releases/download/c-${TERMUX_PKG_VERSION}/msgpack-c-${TERMUX_PKG_VERSION}.tar.gz
TERMUX_PKG_SHA256=420fe35e7572f2a168d17e660ef981a589c9cbe77faa25eb34a520e1fcc032c8
TERMUX_PKG_AUTO_UPDATE=true
TERMUX_PKG_UPDATE_VERSION_REGEXP="\d+\.\d+\.\d+"
TERMUX_PKG_BREAKS="libmsgpack-dev"
TERMUX_PKG_REPLACES="libmsgpack-dev"
TERMUX_PKG_BUILD_IN_SRC=true
TERMUX_PKG_EXTRA_CONFIGURE_ARGS="
-DMSGPACK_BUILD_EXAMPLES=OFF
-DMSGPACK_BUILD_TESTS=OFF
"

termux_pkg_auto_update() {
	# Get latest release tag:
	local tag
	tag="$(termux_github_api_get_tag "${TERMUX_PKG_SRCURL}")"
	# check if this is not a c++ release:
	if grep -qP "^c-${TERMUX_PKG_UPDATE_VERSION_REGEXP}\$" <<<"$tag"; then
		termux_pkg_upgrade_version "$tag"
	else
		echo "WARNING: Skipping auto-update: Not a C release($tag)"
	fi
}
Initial push 2015-06-13 01:03:31 +02:00			`TERMUX_PKG_HOMEPAGE=https://github.com/msgpack/msgpack-c/`
libmsgpack: update to 4.0.0 2021-09-29 16:30:28 +02:00			`TERMUX_PKG_DESCRIPTION="MessagePack implementation for C"`
add licenses for more packages 2019-01-21 13:53:58 +01:00			`TERMUX_PKG_LICENSE="Apache-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 14:16:34 +01:00			`TERMUX_PKG_MAINTAINER="@termux"`
libmsgpack: update to 4.0.0 2021-09-29 16:30:28 +02:00			`TERMUX_PKG_VERSION=4.0.0`
			`TERMUX_PKG_SRCURL=https://github.com/msgpack/msgpack-c/releases/download/c-${TERMUX_PKG_VERSION}/msgpack-c-${TERMUX_PKG_VERSION}.tar.gz`
			`TERMUX_PKG_SHA256=420fe35e7572f2a168d17e660ef981a589c9cbe77faa25eb34a520e1fcc032c8`
auto updates: migrate config from github-projects.txt to build.sh-specific Re-enable automatic updates after deleting github-projects.txt. %ci:no-build 2021-10-04 12:43:31 +02:00			`TERMUX_PKG_AUTO_UPDATE=true`
fix: rename TERMUX_PKG_AUTO_UPDATE_TAG_REGEXP to TERMUX_PKG_UPDATE_VERSION_REGEXP why? since we get versions not tag when updating from repology %ci:no-build Signed-off-by: Aditya Alok <dev.aditya.alok@gmail.com> 2022-04-01 09:41:46 +02:00			`TERMUX_PKG_UPDATE_VERSION_REGEXP="\d+\.\d+\.\d+"`
no more develsplit + provide static libraries as separate package %ci:no-build 2019-07-20 10:42:33 +02:00			`TERMUX_PKG_BREAKS="libmsgpack-dev"`
			`TERMUX_PKG_REPLACES="libmsgpack-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 17:28:41 +02:00			`TERMUX_PKG_BUILD_IN_SRC=true`
libmsgpack: Update from 2.1.3 to 2.1.5 2017-08-07 21:13:58 +02:00			`TERMUX_PKG_EXTRA_CONFIGURE_ARGS="`
			`-DMSGPACK_BUILD_EXAMPLES=OFF`
			`-DMSGPACK_BUILD_TESTS=OFF`
			`"`
fix(libmsgpack{,-cxx}): check name of tag before auto updating upstream uses 'c-' and 'cpp-' prefix in tag name to distinguish release, but both releases are from same repository, so auto update system confuses release of one package to be of another. Now we explicitly check tag name before auto-updating. %ci:no-build Signed-off-by: Aditya Alok <dev.aditya.alok@gmail.com> 2022-04-02 15:50:05 +02:00
			`termux_pkg_auto_update() {`
			`# Get latest release tag:`
			`local tag`
			`tag="$(termux_github_api_get_tag "${TERMUX_PKG_SRCURL}")"`
			`# check if this is not a c++ release:`
fix(libmsgpack{,-cxx}): regexp in tag name check %ci:no-build Signed-off-by: Aditya Alok <dev.aditya.alok@gmail.com> 2022-04-05 20:20:12 +02:00			`if grep -qP "^c-${TERMUX_PKG_UPDATE_VERSION_REGEXP}\$" <<<"$tag"; then`
refactor(auto update): replace `pkg_dir` with `TERMUX_PKG_BUILDER_DIR` - this variable will store path of directory containing packages `build.sh` file. - this is a more standard approach than specifying `pkg_dir` each time Signed-off-by: Aditya Alok <dev.aditya.alok@gmail.com> 2022-04-20 20:01:54 +02:00			`termux_pkg_upgrade_version "$tag"`
fix(libmsgpack{,-cxx}): check name of tag before auto updating upstream uses 'c-' and 'cpp-' prefix in tag name to distinguish release, but both releases are from same repository, so auto update system confuses release of one package to be of another. Now we explicitly check tag name before auto-updating. %ci:no-build Signed-off-by: Aditya Alok <dev.aditya.alok@gmail.com> 2022-04-02 15:50:05 +02:00			`else`
fix(libmsgpack{,-cxx}): regexp in tag name check %ci:no-build Signed-off-by: Aditya Alok <dev.aditya.alok@gmail.com> 2022-04-05 20:20:12 +02:00			`echo "WARNING: Skipping auto-update: Not a C release($tag)"`
fix(libmsgpack{,-cxx}): check name of tag before auto updating upstream uses 'c-' and 'cpp-' prefix in tag name to distinguish release, but both releases are from same repository, so auto update system confuses release of one package to be of another. Now we explicitly check tag name before auto-updating. %ci:no-build Signed-off-by: Aditya Alok <dev.aditya.alok@gmail.com> 2022-04-02 15:50:05 +02:00			`fi`
			`}`