Go to file

Günther Noack 78b3381ef8 Indirect explicit_bzero through memset pointer. The original comment indicates that using `bzero()` directly may result in dead store elimination, so they explicitly avoided calling `bzero()` as you do now. `explicit_bzero` is used in cryptographic software to clear keys from process memory after use, even if that memory is not read any more afterwards. Maybe it would be safer like this? (I copied the approach from https://android.googlesource.com/platform/external/openssh/+/refs/tags/android-6.0.1_r70/openbsd-compat/explicit_bzero.c, so that should work on Android.) Caveat, I was hand-editing the diff and did not find time to set up the toolchain to build this; but the general approach should work?		2020-03-29 23:03:21 +03:00
.github	CI: show checksums for built debs	2020-03-12 19:02:27 +02:00
disabled-packages	move 'swift' to disabled packages	2020-02-17 13:47:32 +02:00
ndk-patches	ndk-patches: do not hide _FILE_OFFSET_BITS=64	2019-12-29 20:56:22 +02:00
packages	Indirect explicit_bzero through memset pointer.	2020-03-29 23:03:21 +03:00
sample	update sample script for new package	2019-08-10 18:01:57 +03:00
scripts	build-package.sh: verify release files with gpg when doing autobuilds (#5062 )	2020-03-21 16:30:02 +02:00
.gitattributes	Update .gitattributes (#872 )	2017-03-22 21:12:16 +01:00
.gitignore	Add vagrant (#642 )	2017-01-03 19:05:15 +01:00
BACKERS.md	Markdown New Guideline Compliance	2019-02-15 18:01:09 +02:00
LICENSE.md	avoid long lines in LICENSE.md	2019-06-08 14:40:01 +03:00
README.md	update readme	2020-02-07 15:41:38 +02:00
build-all.sh	enable on-device builds	2019-08-08 16:58:34 +03:00
build-package.sh	build-package.sh: fix unbound variable error	2020-03-23 23:45:11 +02:00
clean.sh	packages: standardize values of several control variables for build.sh	2019-08-12 18:49:13 +03:00

README.md

Termux packages

This project contains scripts and patches to build packages for the Termux Android application.

The packages available here are only from main set. We have some additional repositories:

https://github.com/termux/game-packages

Game packages, e.g. angband or moon-buggy.
https://github.com/termux/science-packages

Science-related packages like gap and gnucap.
https://github.com/termux/termux-root-packages

Packages which can be used only on rooted devices. Some stuff available here requires custom kernel (like aircrack-ng or lxc).
https://github.com/termux/unstable-packages

Staging repository. Packages that are not stable are only available here.Most likely, new packages will also be placed here.
https://github.com/termux/x11-packages

Packages that require X11 Windows System.

Termux package management quick how-to available on https://wiki.termux.com/wiki/Package_Management. To learn about using our build environment, read the Developer's Wiki.

Project structure

Directories:

disabled-packages:

Packages that cannot be published due to serious issues.
ndk-patches:

Our changes to Android NDK headers.
packages:

Main set of packages.
sample:

Sample structure for creating new packages.
scripts:

Set of utilities and build system scripts.

Contributing

Bug reports

Please, use templates for submitting bug reports. The bug report issue template can be initialized by clicking on https://github.com/termux/termux-packages/issues/new?template=bug_report.md.

General requirements for bug reports are:

All packages are up-to-date.
Problem is not related to third-party software.
Output of termux-info attached.
Be ready to provide more info if requested.

New packages

Use the package request template: https://github.com/termux/termux-packages/issues/new?template=package_request.md.

General requirements for new packages are:

Packages should be open source and have widely recognised OSS licenses like GNU GPL.
Packages should not be installable via language-specific package managers such as gem, pip or cpan.
Packages should not be outdated dead projects.
Be ready that your package request will not be processed immediately.

Pull Requests

All pull requests are welcome.

We use Github Actions for processing all pushes including pull requests. All build logs and artifacts are public, so you can verify whether your changes work properly.

People who are new for packaging can begin with sending PRs for updating packages. Check the outdated packages on https://repology.org/projects/?inrepo=termux&outdated=1.

Get started with information available on Developer's Wiki.

Contacts

General Mailing List: https://groups.io/g/termux
Developer Mailing List: https://groups.io/g/termux-dev
Developer Chat: https://gitter.im/termux/dev or #termux/development on IRC/freenode.

If you are interested in our weekly development sessions, please check the https://wiki.termux.com/wiki/Dev:Development_Sessions. Also, you may want to check the https://wiki.termux.com/wiki/Development.