termux-packages/packages/capnproto/build.sh

TERMUX_PKG_HOMEPAGE=https://capnproto.org/
TERMUX_PKG_DESCRIPTION="Data interchange format and capability-based RPC system."
TERMUX_PKG_LICENSE="MIT"
TERMUX_PKG_MAINTAINER="@termux"
TERMUX_PKG_VERSION=0.9.1
TERMUX_PKG_SRCURL=https://capnproto.org/capnproto-c++-${TERMUX_PKG_VERSION}.tar.gz
TERMUX_PKG_SHA256=83680aaef8c192b884e38eab418b8482d321af6ae7ab7befa3a9370b8e716aad
TERMUX_PKG_BUILD_IN_SRC=true
TERMUX_PKG_FORCE_CMAKE=true
new package: capnproto (#5813) 2020-09-25 08:27:15 -06:00			`TERMUX_PKG_HOMEPAGE=https://capnproto.org/`
			`TERMUX_PKG_DESCRIPTION="Data interchange format and capability-based RPC system."`
			`TERMUX_PKG_LICENSE="MIT"`
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"`
capnproto: update to 0.9.1 2021-10-04 16:53:47 +01:00			`TERMUX_PKG_VERSION=0.9.1`
new package: capnproto (#5813) 2020-09-25 08:27:15 -06:00			`TERMUX_PKG_SRCURL=https://capnproto.org/capnproto-c++-${TERMUX_PKG_VERSION}.tar.gz`
capnproto: update to 0.9.1 2021-10-04 16:53:47 +01:00			`TERMUX_PKG_SHA256=83680aaef8c192b884e38eab418b8482d321af6ae7ab7befa3a9370b8e716aad`
new package: capnproto (#5813) 2020-09-25 08:27:15 -06:00			`TERMUX_PKG_BUILD_IN_SRC=true`
			`TERMUX_PKG_FORCE_CMAKE=true`
apache2, asciidoctor, capnproto: trigger rebuild 2021-10-04 17:50:11 +01:00