Also make sure that steps are in same order as in build-package.sh |
||
---|---|---|
.github/ISSUE_TEMPLATE | ||
disabled-packages | ||
docs | ||
ndk-patches | ||
packages | ||
scripts | ||
.gitattributes | ||
.gitignore | ||
.gitlab-ci.yml | ||
.travis.yml | ||
BACKERS.md | ||
Gemfile | ||
LICENSE.md | ||
README.md | ||
Rakefile | ||
build-all.sh | ||
build-package.sh | ||
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.
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.