You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Michal Bednarski 651936f70f proot: Update for nested chroot() support 6 years ago
.github update readme 6 years ago
disabled-packages Revert "frobtads, sl, unrar: disable packages because their license is not accepted by hosting" 6 years ago
docs build-package: mv code for creating subpackages to new file 6 years ago
ndk-patches update ndk-patches to prevent creation of *.orig files in ./sysroot/usr/include 6 years ago
packages proot: Update for nested chroot() support 6 years ago
scripts CI: skip packages that have long build time 6 years ago
.cirrus.yml CI: better way to pass packages between tasks 6 years ago
.gitattributes Update .gitattributes (#872) 8 years ago
.gitignore Add vagrant (#642) 8 years ago
BACKERS.md Markdown New Guideline Compliance 6 years ago
LICENSE.md Markdown New Guideline Compliance 6 years ago
README.md update readme 6 years ago
build-all.sh build-package: download dependencies recursively when fast-building 6 years ago
build-package.sh build-package.sh: make sure that termux_error_exit() is defined before throwing any errors 6 years ago
clean.sh Change clean-rebuild-all.sh to clean.sh 8 years ago

README.md

Termux packages

Powered by JFrog Bintray

Build Status Join the chat at https://gitter.im/termux/termux

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

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.