Go to file
Leonid Pliushch 2cbd644b08 mariadb: bump package epoch to allow downgrading 2019-09-24 18:49:43 +03:00
.github funding.yml: fill with necessary data 2019-08-11 17:31:57 +03:00
disabled-packages help2man: enable package 2019-08-16 15:37:57 +03:00
ndk-patches Define __TERMUX__ and __TERMUX_PREFIX__ 2019-09-19 21:34:04 +02:00
packages mariadb: bump package epoch to allow downgrading 2019-09-24 18:49:43 +03:00
sample update sample script for new package 2019-08-10 18:01:57 +03:00
scripts Define __TERMUX__ and __TERMUX_PREFIX__ 2019-09-19 21:34:04 +02:00
.cirrus.yml CI: use custom `git clone` for upload task 2019-09-10 17:16:11 +03:00
.gitattributes
.gitignore
BACKERS.md
LICENSE.md
README.md update readme 2019-09-22 18:28:44 +03:00
build-all.sh enable on-device builds 2019-08-08 16:58:34 +03:00
build-package.sh build-package.sh: use absolute paths when sourcing parts from scripts/build/ 2019-08-16 23:19:11 +03:00
clean.sh packages: standardize values of several control variables for build.sh 2019-08-12 18:49:13 +03:00

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.

There available packages only from main set. We have some additional repositories:

Termux package management quick how-to available on https://wiki.termux.com/wiki/Package_Management. To learn about using our build environment, read the Developer's Wiki.

Project structure

There 2 main branches available:

  • master - packages for Android 7.0 or higher.

    Packages are built automatically by CI and published on Bintray.

  • android-5 - packages for Android versions 5.x - 6.x.

    Packages are built by @fornwall and published on https://termux.net.

Directories:

  • disabled-packages:

    Packages that cannot be published due to serious issues.

  • ndk-patches:

    Our changes to Android NDK headers.

  • packages:

    Main set of packages.

  • sample:

    Sample structure for creating new packages.

  • scripts:

    Set of utilities and build system scripts.

Contributing

Bug reports

Please, use templates for submitting bug reports. The bug report issue template can be initialized by clicking on https://github.com/termux/termux-packages/issues/new?template=bug_report.md.

General requirements for bug reports are:

  • All packages are up-to-date.

  • Problem is not related to third-party software.

  • Output of termux-info attached.

  • Be ready to provide more info if requested.

New packages

Use the package request template: https://github.com/termux/termux-packages/issues/new?template=package_request.md.

General requirements for new packages are:

  • Packages should be open source and have widely recognised OSS licenses like GNU GPL.

  • Packages should not be installable via language-specific package managers such as gem, pip or cpan.

  • Packages should not be outdated dead projects.

  • Be ready that your package request will not be processed immediately.

Pull Requests

All pull requests are welcome.

We use CI for processing all pushes including pull requests. All build logs and artifacts are public, so you can verify whether your changes work properly.

People who are new for packaging can begin with sending PRs for updating packages. Check the outdated packages on https://repology.org/projects/?inrepo=termux&outdated=1.

Get started with information available on Developer's Wiki.

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.