a tool that allows you to build packages for multiple systems in multiple formats (deb, rpm, nix, flatpak, snap, etc.).

Given flatpaks and snaps are toxic, the other ones - deb, rpm, pkg - can be packaged relatively easily. It’s all a separate effort with files and meta-info that doesn’t often intersect, but it’s manageable. It lends itself incredibly well to the trivial ‘automation’ that gitlab, forgejo and other major git suites provide.

Source: did this for the entirety I built and maintained a software suite for linux and unix,m for like 15 years. I built some code, I packaged it. Because anything less isn’t really ISO27002.

TL;DR - the ‘tool’ is a simple script and your brain. It’s easy work once you overcome the fear of the unknown and start doing it.

makefile which packages as tarball, deb, rpm and appimage.

Packaging an RPM in a makefile? That’s inside-out.

1. find something Lennart built. Eg. systemd
2. remove that
3. go to 1

till

\sigh

I thought it was naive as well, but because they based it on a mayfly distro that has really great validation and reliability but it’s gone in a fortnight.

Wither Almalinix or Cloudlinux or PCLinuxOS or Mandriva? Three of them have really solid support structures and at least one of them has amazing compatibility options with libraries for services.

There are options. A few of them could be better than fedora while fedora is still owned by redhat as redhat dies from suffocation – hell, its all just fucking ancillary bull (Ansible) they sell now, as its metastatic cancer (Systemd) eats it alive.

Having seen SuSE destroy collaborators like OL, CNC and probably Turbo, I’m okay never even working with them as a customer. I intend to avoid them until death.

Asking the crucial question.

Wow, what a wall of text. I’m sorry but I’m sure I skimmed some parts.

Look. The bulk of the replies you’re going to get will be like “this is my favourite distro and here’s how it works for you” not “this is the best distro for your criteria.” It’s important to understand the deep level of bias you’re going to get.

But your cause is a noble one. I use a particular style of distro because it can be trusted to install well, back out well, do both safely, and allow validation at every stage. I think it’s a good candidate, and it’s already been mentioned as a really great ‘set it and forget it’ distro.

Good luck.

I didn’t get past the ‘u’ part, like it’s pre-T9 texting.

The only thing they offer is bare source?

I like they’ve just given up on trying to understand things like filesystem layouts and fucking systemd - which is cool - but now they own dependency hell and inconsistent installs in trade.

Nah. I’ll get a package where I can confirm the contents, check the sigs, reproduce the build and then deploy it with its dependencies in a reliable, verifiably-consistent process.

https://rhel.pkgs.org/9/epel-x86_64/tor-0.4.8.14-1.el9.x86_64.rpm.html

Sources, sigs, signed BoM. Wheeee!

will only work on specific arm computers anyway.

For now.

Gilliam esc

Gilliam-esque? Gibson-esque?

Well it’s also a US company.

Are you suggesting a US company that shoots rockets to the moon can’t be arsed to follow even a global standard? Like, who the hell else can it be doing business with if the Imperial standard from a king 200 years ago is its ride-or-die baggage?

opensource

Still two words.

Removed by mod

How did it play under Linux?

Look, I’d get my Mom to switch to linux if she still had a chance to play warcraft. Does it play on a rolling RPM release so I don’t have to periodically reinstall the OS? I’m serious. This is almost the only reason I don’t switch the family – very particular games.

This seems to be a dependency failure.

I’m sad that we had this solved 20 years ago. It’s like Texas measles.