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 git@github.com:schra/pkgbuilds.git
cd pkgbuilds
aurpublish setup

1. Adjust the PKGBUILD

2. Update the hash values: updpkgsums PKGBUILD

3. Build, install and manually test if the package works: makepkg -scfi

4. 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
   

5. 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 and provides entries that point to the non-Git package equivalent.
  • Have a pkgver function, so that the pkgver variable gets updated automatically.

• 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 in package(). Never use pkgname in package(), only use it in source.
  • _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 using cd.