Commit Graph

10 Commits

Author SHA1 Message Date
Aditya Alok 9613b79884
upgpkg(main/shellharden): to 4.3.0
Signed-off-by: Aditya Alok <dev.aditya.alok@gmail.com>
2022-06-29 22:03:30 +05:30
Aditya Alok 7713bc3d4e
fix(main/shellharden): use `newest-tag` for auto-update
* it doesn't have releases, only tags

Signed-off-by: Aditya Alok <dev.aditya.alok@gmail.com>
2022-06-29 22:03:30 +05:30
Leonid Pliushch 27afd9e665
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 13:43:31 +03:00
Leonid Pliushch 37375312b9
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
Leonid Pliushch 9c9e7f65b8 update maintainer info
Specifying Termux org members is more correct as we don't have repo-specific
maintainers for termux-packages.

DEB control field specification doesn't allow to specify multiple people as
package maintainers. Value "Termux members @termux" will be used as default
for that field which can be overridden on per-package basis if needed.

%ci:no-build
2020-05-13 11:05:52 +03:00
Leonid Pliushch 93e27997f2 shellharden: update to 4.1.2 2020-02-24 19:47:33 +02:00
Fredrik Fornwall 356322a5c2 shellharden: Update from 4.1 to 4.1.1 2019-08-23 10:09:10 +02:00
Leonid Pliushch c352216c63 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:49:13 +03:00
Leonid Pliushch cc037459aa update maintainer fields where needed
[skip ci]
2019-05-16 19:54:59 +03:00
Leonid Pliushch 0d1920a061 move some packages from unstable repository
New packages that will be added:

 * antiword
 * beanshell
 * cabextract
 * deutex
 * direnv
 * exiv2
 * git-lfs
 * gitea
 * hoedown
 * httrack
 * iverilog
 * links
 * loksh
 * mksh
 * mktorrent
 * pdfgrep
 * shellharden
 * swig
 * tidy
 * tweego
 * wordgrinder
2019-05-11 18:36:47 +03:00