Hi ! I just made my first AUR package, which was really fun, and I was wondering what your own experience was like. Why did you decide to make your first packages ? What was fun, what was annoying ? What problems did you have ? Had you been using Arch for long ?
Mine was nothing complicated, just packaging a bash game with no dependencies made by someone else… because I wanted to try it and I was too lazy to install it from source 😅 Just the thought of having to manually check for updates and reinstall exhausts me and my adhd calculated that learning how to make a package would be less effort (never try to argue with adhd maths).
I did have some trouble because the game wanted its config and other files in $HOME and didn’t create them directly (it was done by an install script run when installing it manually from source), but obviously I couldn’t make the package create them there, which really confused the hell outta me. In the end the creator of the game kindly send me links to AUR packages that other people had done for his other projects so I could see what they had done and I did and did the same, which was to put the files in the locations recommended by the specs like /etc and /usr, and to added a post-install message telling the user to copy/paste some commands to copy the files in $HOME. It’s a bit clunky but I guess it works 🥳
The fun part for me was learning more about how packages were installed, and the reason behind the specs. It’s fine reading that packages shouldn’t create files in $HOME but it doesn’t tell me WHY. Also it’s a lot more fun to try anyway even knowing it’s a bad idea, just to see what kind of mess happens (turns out it couldn’t install because /root/.config was missing 😂 )
If you had told me a year and a half ago when I switched to linux that I’d end up making a package, I’d probably have thought that you were crazy 😁
I’ve never made an arch package, but i did make a few void linux templates and nix derivations. I’ve never actually officially submitted them, just kept them in my own repo cause i wasn’t sure if i was up for maintaining them. The void templates were pretty easy to learn, they have good documentation on their github. The packages that i made templates of were pretty simple so it didn’t require too much skill or knowledge. It’s basically a bunch of bash scripts/variables/funtions that automate the build process and builds the package inside of a fake chroot. Nix derivations were a bit more tricky, eventhough the packages i built were pretty simple, just like void, but nix is… well… nix lol. often times things are more complicated in nix, but i do like using it. The main reason i wanted to make my own packages is because i hate manually compiling stuff, and littering my system with build dependencies, so i felt like it was worth learning how to automate it. At the moment i’m also busy with setting up dwl (dwm, but for wayland), which is something i never thought i would do, since i try to avoid having to compile things, but nix actually makes it super easy to add patches and my own config.h through overlays and overrides, so it’s been pretty straightforward so far.