AUR is cool. It is very cool. Almost any user can upload packages to it and if they gain popularity they can also be moved to the official repositories. But there are several problems with AUR.
If you want to integrate AUR Packages into your custom archiso build you have to host a repository for them yourself. But hosting them yourself has the problem that you may miss out updates of the packages and your self-hosted repository will be outdated very soon if you don´t update it manually by hand.
There are several approaches to solve the problem of automated builds for AUR Packages. A list of emamples:
But it was not that i was searching for. I wanted something automated. Something that i can schedule every week or every day, to push the newest images to my repository.
I already used Drone CI so i sticked with it and built a pipeline generator for it. It's a bash script that can be used to generate the .drone.yml. But lets start first with the things you will need to build this pipeline yourself:
- A installed Sonatype Nexus Repository
- A working Drone CI instance
- A Git Server or Gitlab Repository (Github is not recommended because of the file upload limitations)
- Fork the Github Repository
- Connect Drone CI with your Git Repository and activate it
- Clone your Repository
- Remove ananicy package from the repository (it is just a example package)
- Add the packages you want
git submodule add https://aur.archlinux.org/timeshift.git timeshift
6. Register the Packages you want in the packages.txt. You can add commands that should be executed first, before building the package with an ^. So for example if you want to install nano before installing timeshift register the package like this in the packages.txt (every package in a single line).
timeshift^pacman -Sy --noconfirm nano
7. Change the variables in the buildDrone.sh. For example the volumepath describes where the shared volume for all pipeline steps is mounted. This is important because this i later the name you add into your pamac.conf. Also change the apiurl to the API URL of your Nexus Instance.
8. Change buildjob.txt to your needs. So for example change the environemt variables to your Nexus instance and change the mountpoint in the commands to your repo name.
9. run buildDrone.sh and push the changes to your repository.
10. Change timeout of the Drone Repository, because it may take longer than 60 minutes to build your packages.
11. Add anonymous role in your Nexus Repository so your raw Nexus Repository can be read by anybody.
The pipeline should build your packages and pushs the packages to your Nexus Raw Repository.