Are you building a C/C++ project that should run on BSD, Gnu/Linux and other platforms? Then maybe use autotools. All distro tooling will easily be able to handle it.

Are you just building some small project that will never make it into a distro, maybe just use something simpler. Or even just a plain makefile.

I understand how this could be a prime target of a supply chain attack and that things are a bit fishy. On the other hand people are waaaay less picky about installing other binary blobs on their machines. I wish paranoia would be more general :)

Yeah, very nice. It will be tough to bootstrap since you need a critical mass of people who ideally live close together so that it’s cheap and quick enough to deliver the items in question.

I’ll give it a try. Nothing to loose.

Me too

A floss project’s success is not necessarily marked by its market share but often by the absolute benefit it gives to its users. A project with one happy user and developer can be a success.

Flatpaks won’t get their libs updated all at once by just updating a library. This can be very bad in cases like bugs in openssl. Instead of just updating one library and all other software benefiting from the fix, with flatpaks, you need to deal with updating everything manually and waiting for the vendor to actually create an update package.

I’m not 100% sure about this. Flatpak has some mechanisms that would allow to manage dependencies in a common fashion.

Why in Louvre though?

These bastards!

I’d be more than happy if this was used. Do whatever you want with it as long as you abide by the CC BY-SA-4.0 license. This means you can share freely and modify as long as you keep the authorship information and share with same license.

I agee but also… They are just waaay too handy and unreplacable for many folks. So many peoples lives rely on these machines and taking them away would need dramatic change for those people.