This repository contains packages for Arch Linux. These packages are also published in the AUR.
I'm using aurpublish to maintain this repository.
git clone [email protected]:schra/pkgbuilds.git
cd pkgbuilds
aurpublish setup
-
Adjust the
PKGBUILD
-
Update the hash values:
updpkgsums PKGBUILD
-
Build, install and manually test if the package works:
makepkg -scfi
-
Commit the
PKGBUILD
.aurpublish
will prefill the commit message. In most cases you can just leave the commit message like that.cd PACKAGE/ git add PKGBUILD git commit
-
Push the package to both the AUR and this repository
aurpublish PACKAGE git push
-
If possible, I always provide both the Git and non-Git packages.
-
All Git packages need to:
- Have
conflicts
andprovides
entries that point to the non-Git package equivalent. - Have a
pkgver
function, so that thepkgver
variable gets updated automatically.
- Have
-
I try to keep the diff between the Git and non-Git PKGBUILDs as small as possible. That's why I always define the
_name
and_mainfolder
variables:_name
is the package name without the-git
suffix (if there is any). It is used to install files in the file system inpackage()
. Never usepkgname
inpackage()
, only use it insource
._mainfolder
is the folder that contains the source code. For Git packages this is the repository name. For non-Git packages it is the name of the folder inside the tar ball (normally tar balls contain exactly one directory which then contains the actual content). Use_mainfolder
when usingcd
.