> Open Build Service

I heard about that before, but never tried. How in practice do you deal with conflicting library versions?

> It just doesn't look like "the future of application distribution", https://nixos.org/ does.

Strongly agree. I just find it sad that nix/guix doesn't have proper desktop integration (to my knowledge), and that nix requires nixGL hacks to start any GUI on foreign distros.

Basically you write spec file for rpm (or debian/control for deb) and put your dependencies there as usual. But for each supported distro you can override packages names in OBS project config, so if the same package called differently in another distro you substitute it without modifying spec-file. Here's how it looks: https://build.opensuse.org/projects/home:oleg_antonyan/prjco...

It's a mess, without meaningful documentation and lots of bugs I've spent hours digging the source code to get any idea of how to use it.

I build everything static except Qt. My project is small enough with only 4 external libraries, so it's ok atm.

Why would you rather install some random rpm from someone you don't know as opposed to a flatpak?

This works both ways: Why would you rather install some random flatpak from someone you don't know as opposed to a rpm?

The trust is outside of the scope of package managers

Because installing an rpm allows you to run arbitrary code as root. Installing a flatpak does not. I mean there are many more reasons but that should be en.

It's explained in the article, security section: b/c installing flatpak can also run arbitrary code as a user. And I won't argue that running malicious code as a user is always harmless. Regardless of root access if you're installing flatpak and its author want to pwn you - they can do it even without root access

Yeah, so why even have user accounts and not just root everything? I mean if there's no difference...

If the future of application distribution looks like learning a new language just get things installed, count me out. Linux is obtuse enough as it is.