termux-packages/packages/muchsync/build.sh

TERMUX_PKG_HOMEPAGE=http://www.muchsync.org/
TERMUX_PKG_DESCRIPTION="Synchronize notmuch mail across machines"
TERMUX_PKG_LICENSE="GPL-2.0"
TERMUX_PKG_MAINTAINER="@termux"
TERMUX_PKG_VERSION=5
TERMUX_PKG_SRCURL=http://www.muchsync.org/src/muchsync-${TERMUX_PKG_VERSION}.tar.gz
TERMUX_PKG_SHA256=8b0afc2ce2dca636ae318659452902e26ac804d1b8b1982e74dbc4222f2155cc
TERMUX_PKG_DEPENDS="libc++, libsqlite, libxapian, notmuch, openssl"
new package: muchsync (#5027) 2020-03-13 12:37:24 +01:00			`TERMUX_PKG_HOMEPAGE=http://www.muchsync.org/`
			`TERMUX_PKG_DESCRIPTION="Synchronize notmuch mail across machines"`
			`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 14:16:34 +01:00			`TERMUX_PKG_MAINTAINER="@termux"`
new package: muchsync (#5027) 2020-03-13 12:37:24 +01:00			`TERMUX_PKG_VERSION=5`
			`TERMUX_PKG_SRCURL=http://www.muchsync.org/src/muchsync-${TERMUX_PKG_VERSION}.tar.gz`
			`TERMUX_PKG_SHA256=8b0afc2ce2dca636ae318659452902e26ac804d1b8b1982e74dbc4222f2155cc`
			`TERMUX_PKG_DEPENDS="libc++, libsqlite, libxapian, notmuch, openssl"`