posted in Technology
I hate packaging my software for Linux (fresh)
getfresh.dev/docs/blog/packaging-for-linux/No automatic updates for .deb / .rpm
The author seems to have completely missed the point that they can just publish their own repositories to allow users on both of these platforms to update. It would also mean they could avoid the problems they’re having building source packages.
Their complaints about supporting instalations with older libc versions are also addressable by just building against the oldest libc they wish to support.
Replying to @notabot@piefed.social
that defeats the purpose of a package manager
Not really. The user adds the repository to the list of repositories their package manager is using, and the packages in that repository appear as normal packages for them to select. When the author publishes a new version of their package it’ll appear as an update in all users package managers.
Replying to @notabot@piefed.social
The user adds the repository to the list of repositories their package manager is using,
Fun fact: when we were doing devops as config management, we distributed repository configs AS packages … which we updated as required.
and the packages in that repository appear as normal packages for them to select. When the author publishes a new version of their package it’ll appear as an update in all users package managers.
So easy.
These days, with CI, ya berge your patch and the fix is built and sent to testing immediately, ready to be assessed for promotion, which then signs and pushes the artifact into the pipeline for synchronization and application everywhere.
Aside from the actual smarts to build a good package, the tooling makes every other part of is zero-friction.