Contains PKGBUILD files for creating Arch Linux packages:
- Packages for my own applications and libraries such as Syncthing Tray, Tag Editor, Password Manager, ...
- Packages I maintain in the AUR:
- misc packages, eg. Gogs/Gitea, Subtitle Composer, openelec-dvb-firmware
- mingw-w64 packages which allow to build for Windows under Arch Linux, eg. freetype2 and Qt 5
- apple-darwin packages which allow to build for MaxOS X under Arch Linux, eg. osxcross and Qt 5
- Other packages imported from the AUR to build with slight modifications
So if you like to improve one of my AUR packages, just create a PR here.
Each package is in its own subdirectoy:
default-pkg-name is the default package name (eg.
variant usually one of:
default: the regular package
hg: the development version
mingw-w64: the Windows version
apple-darwin: the MacOS X version
The repository does not contain
Contributing to patches
Patches for most packages are managed in a fork of the project under my GitHub profile. For instance,
mingw-w64-qt5-base are managed at github.com/Martchus/qtbase.
I usually create a dedicated branch for each version, eg.
5.10.1-mingw-w64. It contains all the patches based on
Qt 5.10.1. When doing fixes later on, I usually preserve the original patches and create a new branch, eg.
So in this case it would make sense to contribute directly there. To fix an existing patch, just create a fixup commit. This (unusual) fixup workflow aims to keep the number of additional changes as small as possbile.
To get the patches into the PKGBUILD files, the script
devel/qt5/update-patches.sh is used.
Mass rebasing of Qt patches
This is always done by me. Please don't try to help here because it will only cause conflicts. However, the workflow is quite simple:
devel/qt5/rebase-patches.shon all Qt repository forks
rebase-patches.sh 5.11.0 5.10.1 fixesto create branch
- after fixing possible conflicts, run
- otherwise, that's it
devel/qt5/update-all-patches.shto update PKGBUILDs
Supported build and deployment tools for mingw-w64-qt5 packages
Currently, I test with qmake and CMake. With both build systems it is possible to use either the shared or the static libraries. Please read the comments in the PKGBUILD file itself and the pinned comments in the AUR for futher information.
There are also pkgconfig files, but those aren't really tested.
qbs and windeployqt currently don't work very well (see issues). Using mxedeployqt might be an alternative for windeployqt.
I also provide a binary repository containing the packages found in this repository and a lot of packages found in the AUR.
For more information visit my website.