Go to file

Leonid Pliushch 22811350e5 imagemagick: rebuild due to versioned liblzma		2019-05-03 17:21:10 +03:00
.github	update readme	2019-02-25 00:01:19 +02:00
disabled-packages	Revert "frobtads, sl, unrar: disable packages because their license is not accepted by hosting"	2019-04-12 17:18:14 +03:00
docs	build-package: mv code for creating subpackages to new file	2019-03-07 20:35:32 +01:00
ndk-patches	update ndk-patches to prevent creation of *.orig files in ./sysroot/usr/include	2019-03-20 15:37:12 +02:00
packages	imagemagick: rebuild due to versioned liblzma	2019-05-03 17:21:10 +03:00
scripts	CI: skip packages that have long build time	2019-05-02 22:00:19 +03:00
.cirrus.yml	CI: better way to pass packages between tasks	2019-05-03 00:47:26 +03:00
.gitattributes	…
.gitignore	…
BACKERS.md	Markdown New Guideline Compliance	2019-02-15 18:01:09 +02:00
LICENSE.md	Markdown New Guideline Compliance	2019-02-15 18:01:09 +02:00
README.md	update readme	2019-05-02 19:13:37 +03:00
build-all.sh	build-package: download dependencies recursively when fast-building	2019-03-03 01:40:22 +02:00
build-package.sh	build-package.sh: make sure that termux_error_exit() is defined before throwing any errors	2019-04-20 17:28:39 +03:00
clean.sh	…

README.md

Termux packages

This project contains scripts and patches to build packages for the Termux Android application. Note that packages are cross-compiled and on-device builds are not currently supported.

More information can be found in the docs directory.

Directory Structure

disabled-packages: Packages that cannot be built or have serious issues.
docs: Documentation on how to build, formatting etc.
ndk-patches: Patches for Android NDK headers.
packages: All currently available packages.
scripts: Utility scripts for building.

Issues

The two most common types of issues are package requests and bug reports. There are already templates available.

You can open an issue for any package or build problems. For example, if you observing crashes or other kind of malfunction, you are certainly welcome to file an issue.

Also, if you want to request a particular package, you may suggest it in an issue. However, be prepared that package may not be available shortly. Bugfixes and improvements take precedence over new packages.

Pull Requests

We welcome any pull requests. Nevertheless, a log file should be provided in order to show that it is at least working.

All pull requests will be built by Cirrus CI. Usually, it is expected that all tasks will pass. But do not worry if CI build timed out. Alternatively, you can provide build logs by yourself.

Note that it is highly recommended to keep your pull requests up-to-date. If you do not know how to do this, take a look on manpage of git-rebase.

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.