Achill Gilgenast
7f8facc9d8
Previously the process was that once a branch is EOL, the
notification-commit was cherry-picked from the branch before.
However that makes less sense, since the package then doesn't go
through the same mass updates as pmaports master does, e.g. it still
referenced gitlab.com & -gtk3, and doesn't allow changes by contributors
other than the one cherry-picking it.
Adapted from c088d806ea25 ("main/postmarketos-upgrade-gtk3: new aport")
See https://gitlab.postmarketos.org/postmarketOS/pmaports/-/issues/4197.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7769>
postmarketOS aports repository
This repository contains the APKBUILD files for postmarketOS-specific packages, along with the required patches and scripts, if any.
There are many more packages defined in the Alpine Linux aports on which these packages depend.
Helpful resources:
- How to create a package
- APKBUILD reference
- pmaports commit style
- Review and merging guidelines
- Alpine Linux aports
- Alpine Linux package search
- postmarketOS package search
Git Hooks
You can find some useful git hooks in the .githooks directory.
To use them, run the following command after cloning this repository:
git config --local core.hooksPath .githooks