Go to file
Leonid Pliushch 5fa78ec3ae add CONTRIBUTING.md
Written from scratch, probably subject for improving with parts from https://github.com/termux/game-packages/blob/master/CONTRIBUTING.md...
2020-04-28 02:37:34 +03:00
.github CI: show checksums for built debs 2020-03-12 19:02:27 +02:00
disabled-packages swift: enable package and update to 5.2.1 2020-04-10 13:03:38 +03:00
ndk-patches ndk-patches: do not hide _FILE_OFFSET_BITS=64 2019-12-29 20:56:22 +02:00
packages espeak: build with pcaudiolib 2020-04-27 21:40:36 +03:00
sample update sample script for new package 2019-08-10 18:01:57 +03:00
scripts swift: update from 5.2.1 to 5.2.2 and fix static compilation (#5169) 2020-04-26 12:52:25 +03: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
BACKERS.md Markdown New Guideline Compliance 2019-02-15 18:01:09 +02:00
build-all.sh enable on-device builds 2019-08-08 16:58:34 +03:00
build-package.sh build-package.sh: fix unbound variable error 2020-03-23 23:45:11 +02:00
clean.sh packages: standardize values of several control variables for build.sh 2019-08-12 18:49:13 +03:00
CONTRIBUTING.md add CONTRIBUTING.md 2020-04-28 02:37:34 +03:00
LICENSE.md avoid long lines in LICENSE.md 2019-06-08 14:40:01 +03:00
README.md update readme 2020-02-07 15:41:38 +02:00

Termux packages

Packages last build status Docker image status Repology metadata status Join the chat at https://gitter.im/termux/termux

Powered by JFrog Bintray

This project contains scripts and patches to build packages for the Termux Android application.

The packages available here are 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

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