Hi Tim, sorry for the late response but I had to pause with CRUX for a few days. And hey,
If you want to participate and maintain Pkgfiles, be my guest, I wrote a little guide that is still a WIP and could use a few updates, but I don't have time to do that right now [1]
that is really valuable stuff you compiled here, thank you for sharing best practices! I already started to create a bunch of own packages for some programs I like or regularly use and which I want on my fresh CRUX installation.
It's rather trivial in most cases is all I can say anyway.
Hm, I would not say it is "trivial" because now I know that my first attempts of creating packages only scratched the surface of what is possible and recommended. On the other hand, with only minor fiddling, packaging worked very well so far. And now I have a perfect reference to improve and look for answers to some questions. And yes, agreed, all in all CRUX packaging is really not daunting and follows KISS in an exemplary manner.
Since I am the one maintaining libreoffice (among around 1000 other ports)
I am wondering, how do you manage to maintain 1000 packages and more? That is really impressive! I mean, how do you track which packages are subject to updates, read release notes, etc. How much time, automatization and energy do you put into this task? Concerning your invitation, give me some time to get familiar with CRUX, packaging etc. If nothing unexpected happens, I definitely plan to stick with CRUX and would like to share my package repository and experiences here as well. Best regards, Martin