Enterprise linux operating systems don’t easily support Python3/Pip3.
Even from a deployment perspective, providing a binary makes sense for a python3 package.
Working on https://github.com/FiaasCo/borgbackup taught us deploying a binary of borg made much more sense.
Are there plans to implement a packaging system (such as https://github.com/cmarquardt/borgmatic-binary) for borgmatic?
Can we get this into a feature and start working on it?
Please share your thoughts.
You’ve probably seen it already, but there are a bunch of third-party distribution-specific options for installing borgmatic.
The borgmatic-binary project you linked to though looks like exactly what you’re asking about here. Is the issue that it’s not updated on every borgmatic release, and you’d like something more official or automated?
Also, could you say more about your use case, your Linux distribution, etc? Is the problem that pip just isn’t available at all, or is it an outdated version? Do you normally install things with the enterprise Linux’s package manager, or do you usually install binaries?
The borgmatic-binary would be perfect if it was implemented into borgmatic just as borg does for releasing cross-platform binaries. That way I am able to quickly run borg on a variety of platform/cpus and deploy at scale.
Having widespread packages available for different distributions really is a good thing, but from an automation point of view, it requires adding 1 or more different repositories, packages, .. just to be able to get it to work. Every distribution is almost a custom-job to get it done (ever tried ‘managing’ python3/pip3 packages on CentOS?).
(note: i’m all in favor of using regular packages (rpm/deb/…) but in some cases it causes more trouble than it fixes things if they are not in the main repositories of the distributions)
Having to go through that hassle vs. being able to just take a binary is just a much cleaner option from an automation point of view. It also allows for easy upgrades/downgrades. Borgmatic will be instantly available (platforms,cpus) and much easier to start playing with.
I would be willing to help out and try to implement this with pleasure provided we decide on what needs to be done. (I’m a automation/cicd fanatic, but I lack python dev skills).
The alternative will be to spawn a separate disconnected system to get these binaries built and deployed (much like the person who created the borgmatic-binary project). This is rarely a good thing.
I would also like to have a pre-compiled binary for borgmatic!
It would help with running it on my Unraid server. Currently, I need to re-install it every reboot because packages installed do not persist after a reboot.
With a pre-compiled binary like I am using with Borg, I could just create a symbolic link at boot time rather than have to re-install via pip3 every boot…
No due date set.
This issue currently doesn't have any dependencies.
Deleting a branch is permanent. It CANNOT be undone. Continue?