sergiotarxz
/
termux-packages
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
6,557 Commits 1 Branch 0 Tags 56 MiB
Shell 72.6%
C 18.9%
C++ 4.5%
CMake 1.5%
Python 0.8%
Other 1.5%
Go to file
Fredrik Fornwall 0626265f80 mime-support: Update from 3.61 to 3.62 2019-02-16 00:02:20 +01:00
.github/ISSUE_TEMPLATE
…
disabled-packages No backticks 2019-02-15 18:01:09 +02:00
docs BUILD.md: specify common files where build instructions usually provided 2019-02-15 18:00:24 +02:00
ndk-patches Fix langinfo.h mixup 2019-01-25 02:59:32 +01:00
packages mime-support: Update from 3.61 to 3.62 2019-02-16 00:02:20 +01:00
scripts Dockerfile to tabs 2019-02-15 18:01:09 +02:00
.gitattributes
…
.gitignore
…
.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 Markdown New Guideline Compliance 2019-02-15 18:01:09 +02:00
Gemfile
…
LICENSE.md Markdown New Guideline Compliance 2019-02-15 18:01:09 +02:00
README.md improvements to README.md 2019-02-15 18:00:24 +02:00
Rakefile remove redundant things from CI configuration 2019-01-28 14:20:45 +00:00
build-all.sh build-all.sh: don't use tabs in script usage info 2019-02-15 18:01:09 +02:00
build-package.sh Specify "--path ." when building with cargo 2019-02-15 23:22:13 +01:00
clean.sh
…

README.md

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

Mailing Lists