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.
 
 
 
 
 
 
Fredrik Fornwall f9afd0a7ee Switch from conflicts to breaks for readline 6 years ago
.github update readme 6 years ago
disabled-packages disabled-packages: racket is now in https://github.com/termux/unstable-packages/tree/master/packages/racket 6 years ago
docs BUILD.md: review and fix basic build steps explanation 6 years ago
ndk-patches Initial changes for NDK r19 support 6 years ago
packages Switch from conflicts to breaks for readline 6 years ago
scripts build-package: mv termux_step_finish_build to scripts/build/ 6 years ago
.gitattributes Update .gitattributes (#872) 8 years ago
.gitignore Add vagrant (#642) 8 years ago
.gitlab-ci.yml Remove relevant instructions 6 years ago
.travis.yml remove redundant things from CI configuration 6 years ago
BACKERS.md Markdown New Guideline Compliance 6 years ago
Gemfile Travis pkg builds (#1119) 8 years ago
LICENSE.md Markdown New Guideline Compliance 6 years ago
README.md update readme 6 years ago
Rakefile remove redundant things from CI configuration 6 years ago
build-all.sh build-all.sh: don't use tabs in script usage info 6 years ago
build-package.sh build-package.sh: add short descriptions for package hooks 6 years ago
clean.sh Change clean-rebuild-all.sh to clean.sh 8 years ago

README.md

Termux packages

Powered by JFrog Bintray

pipeline 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.

Normally, all pull requests will be tested by Travis CI. However, in case if you are banned or for whatever reason do no use Travis CI, you should provide a log file by yourself.

All tests for master branch are done by Gitlab CI.

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.