Hi Bert, On 4/23/26 9:55 PM, Bert Peters wrote:
Your packages look nice and clean. I couldn't help but notice that you maintain vagrant-git. I don't know how you manage; we dropped vagrant to the AUR because it didn't work well with our Ruby ecosystem. Nice.
Thanks for reviewing my packages! I occasionally needed vagrant-git when the latest release of vagrant was broken due to ruby dependencies but the fix was already in the upstream repository :) I find vagrant quite useful when I need to reproduce production servers, prototype or write procedures. I really don't use it every day and I'm not brave enough to try bringing it back into extra.
This looks neat. I'd love to pick your brain about that some time.
Actually, I'd like some feedback on this. My goal is not to cover 100% of any software, but at least to verify that a package is usable after installation and that library updates don't break the packages that depend on them. I'd like to cover as many packages from core as possible (given the constraint that it runs in podman containers). I've really tried to keep the code as simple as possible to make the whole project maintainable/understandable on volunteer time. Another objective was to make it easy to write test files with very little overhead, you just have to source one helper script and the tests run almost transparently in an Arch Linux container with the right packages updated from the testing repositories. If you have more questions, don't hesitate to ask.
As you are currently decidedly active on the AUR, would you be interested in helping with AUR moderation (handling orphan/merge/deletion requests) as well?
I can definitely help, but I can't guarantee that I will commit regularly a fixed amount of time on this. That said, I'll do my best ;) Best, -- Hyacinthe