juipeltje

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.