Hey Martin, On 17.11.2021 21:37, Martin Michel wrote:
sorry for the late response but I had to pause with CRUX for a few days.
Don't worry.
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.
Look through core/opt/contrib packages for the best examples. I just put that together when i had a few free minutes but since then never had the time to revisit the guide, even though I want to. Some things I do at least have changed, out of the top of my head, I know pretty much put lto and pie on everything meson.
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.
When you look at a few core/opt/contrib (and compat-32 if you need any of that) you will see that most of them are very very similiar. With that in mind, it narrows down to providing a good basic depends on line as well as a proper footprint, IMO. There is only a few odd ones that really mean work after they are intially are set up.
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?
Abusing coffee and unhealthy sleeping habbits. Like mentioned above, it's often just a number bumping game as well as rebuilding these ports in a container. I have a few scripts to help around the task. I am subscribed to mailing list, watch git repos, monitor some rss feeds and there is repology too. I used opt/ck4up for a long time, but writing a lot of rules in ruby regex just isn't my jam :) But yes, it grew that now it takes a considerable amount of my time. So far, there have not been people that step up and want to officially contribute, and I'd certainly be considering transfering ownership for some of my ports if there ever was somebody seeking to help out. Future plans would involve putting together a CI that would build packages in a clean container, gitlab, buildbot, whatever, and automate it through git (on push hooks for prs generated by a bot maybe?). I am unsure if we could do that with our own ressources, and as far as I know there is no flow of money to the project so paid solutions (for me) are off the table for now. In short, all I am ever saying is we need more people to actively contribute to CRUX.
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.
Don't worry, I am easy on telling that to people because of what I explained above. I am more of a "with the door in hand through the wall" kinda guy. I am glad you enjoy your experience so far! Best regards, Tim