You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Leonid Plyushch 36c35625e8 librsvg: update to 2.46.4 5 years ago
.github funding.yml: fill with necessary data 5 years ago
disabled-packages move abuild and apk-tools to disabled packages 5 years ago
ndk-patches ndk-patches: avoid free()'ing pointer which is still in use 5 years ago
packages librsvg: update to 2.46.4 5 years ago
sample update sample script for new package 5 years ago
scripts cmake: update to 3.16.2 5 years ago
.cirrus.yml CI: specify needed resources on per-task basis 5 years ago
.gitattributes Update .gitattributes (#872) 8 years ago
.gitignore Add vagrant (#642) 8 years ago
BACKERS.md Markdown New Guideline Compliance 6 years ago
LICENSE.md avoid long lines in LICENSE.md 6 years ago
README.md Grammatical correction. 5 years ago
build-all.sh enable on-device builds 5 years ago
build-package.sh build-package.sh: use absolute paths when sourcing parts from scripts/build/ 5 years ago
clean.sh packages: standardize values of several control variables for build.sh 5 years ago

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.

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

There 2 main branches available:

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.