Go to file
Leonid Pliushch f3a395c68b BUILD.md: mention Termux's FHS problem
Termux is not FHS-compliant.
2019-02-15 18:00:24 +02:00
.github/ISSUE_TEMPLATE Add bug_report and package_request templates 2018-12-27 23:55:16 +01:00
disabled-packages Change permissions 2019-02-09 21:06:31 +02:00
docs BUILD.md: mention Termux's FHS problem 2019-02-15 18:00:24 +02:00
ndk-patches Fix langinfo.h mixup 2019-01-25 02:59:32 +01:00
packages vim: Update from 8.1.0850 to 8.1.0900 2019-02-14 00:02:24 +01:00
scripts 3 COPY to 1 2019-02-15 17:27:41 +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
.gitlab-ci.yml gitlab ci: use default expiration time for built artifacts 2019-02-10 22:15:28 +02:00
.travis.yml remove redundant things from CI configuration 2019-01-28 14:20:45 +00:00
BACKERS.md Update BACKERS.md 2018-07-14 00:25:29 +02:00
build-all.sh Improve formatting of parantheses for functions 2019-02-09 21:06:31 +02:00
build-package.sh build-package.sh: minor cleanup 2019-02-10 20:41:35 +01:00
clean.sh Change clean-rebuild-all.sh to clean.sh 2016-09-14 17:57:33 -04:00
Gemfile Travis pkg builds (#1119) 2017-07-10 00:05:36 +02:00
LICENSE.md Update LICENSE.md 2017-08-26 23:06:16 +02:00
Rakefile remove redundant things from CI configuration 2019-01-28 14:20:45 +00:00
README.md Add Windows Instructions 2019-02-15 18:00:24 +02:00

Termux packages

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 that on-device builds are not currently supported.

More information can be found in the docs directory.

Directory Structure

  • disabled-packages: Packages that cannot build or are currently disused.

  • docs: Documentation on how to build, formatting etc.

  • ndk-patches: C Header patches of the Android NDK.

  • 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 there are segmentation faultd or cashes, you are certainly welcome to file an issue.

Also, if you have a package request, you may suggest it in an issue. However, be prepared that we may not be able to provide the package shortly as most contributors are busier and busier.

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 now done in Gitlab CI.

Mailing Lists