Building native packages is complicated | Packaging Anubis as native packages
Building native packages is complicated | Packaging Anubis as native packages
Especially if you want a UX as good as Docker images give you.
Anubis provides protection against bots scraping websites and DDoSing projects.
This blog post is about Xe's reasoning for originally only providing docker packages and their work to provide native packages.
You're viewing a single thread.
There must be a tool that allows you to build packages for multiple systems in multiple formats (deb, rpm, nix, flatpak, snap, etc.). Does that not exist? After 20 years of these systems existing, somebody must've tried...
Also, it's clear that once again, open source needs some kind of funding model, because it's a little crazy that a project like this can get so popular so fast, the dev flooded with praise, thanks, and issues but not money to maintain and develop it.
Problem is that distro1 has req-lib2.5.3 while distro2 has req-lib2.7.8, but your project was developed on distro3 with req-lib2.9.5 so you have to deal with every distro having different lib versions and compatibility issues that come with it, not just different packaging formats.
And different names too. Debian and Fedora have different packages names, so req-lib on debian becomes req-devel on Fedora.
And since Arch is rolling release it's python-lib, not python3-lib. :)
Long time ago I've tried making a makefile which packages as tarball, deb, rpm and appimage.
It's just a goofy attempt.Suse's open build system does this. It's just very enterprisy to me, so I haven't really used it myself