Jacques Plante, who in 1959 was the first NHL goaltender

Woo! 🇨🇦

The zombies in Warm Bodies are insightful, though.

Pierre Poilievre threw his own father under the bus

That’s his father. It doesn’t affect Peter. They’re two different people, so why should he care?

(If you need a sarcasm tag on this, I weep for your teachers)

It’s fun the tangents you go on. I hope it all makes sense to you.

Ooh, nice catch.

That’s 5 years. Nice!

Meanwhile:

• rhel7 still supported on year 14 via tuxcare/alma
• Solaris 10 will end support on year 21
• almalinux vows 25 years support on its el9 offering

Not merely anti-zionism, right? There is anti-Semitism, but that’s not what Mr Trump and his people are triggered by.

again

Did prices normalize and I missed my chance? It seems GPUs, RAM and SSDs haven’t left the stratosphere in a year. The boeing space ship didn’t stay up that long, and it was a boeing and thus not flight-worthy for most of its service period.

maybe ansible

I’ve done Ansible professionally for 3 years, now. I’ve used puppet, chef/cinc, I’ve played with mgmtconfig, and I’ve built entire ecosystems out of cron+make+rpm since 2002, 6 years before ‘devops’ had a name.

Don’t use Ansible. EVERYTHING ELSE is better. Please consider any option before it. Strongly consider mgmtconfig.

OSs

OSes

C’mon, man.

headteacher

What a word to spell wrong.

I looked at .deb as well and boy are there weird things there.

There are many similarities between RPM and pkgbuild for Arch, so I could easily copy almost entire pkgbuilds from AUR and merely adapt a few variables but whatever the inventors of .deb concocted is crazy.

That build method dates back super-far, and probably mirrors unix packaging of the day. This is not a good thing, in that it did miss out on some validation features that RPM and NIX have, and that’s a problem that hasn’t been fixed (in unix or debian) even now (25+ years after we noticed it in the enterprise OS company I worked at, and which invalidated debian even then as a product we wanted to support alongside unix).

What I’m trying to say, is that when people said “just use nix”, they probably really mean to use nix as a platform to build other packages withouth doing extra work.

What you should be saying is something that recognizes that not all systems adhere to FHS. It needs to account for the non-compliant ones, and that includes Lennart’s delightful deviations when he obviously just knew better than the Industry.

This is literally what flat pack was meant to address. Just package has push it and let any system use it. So it is a little more complicated and another step on top of everything.

Flatpak is absolutely terrible. As a second repository, it breaks source of truth, doesn’t share dependency or SBOM data with the system and at worst begs for dependency hell.

At best it’s XKCD 927.

I’m pretty sure that, with a bit of fiddling, you could even put them on a github pages site.

Harbottle does this. It’s very well-done.

The user adds the repository to the list of repositories their package manager is using,

Fun fact: when we were doing devops as config management, we distributed repository configs AS packages … which we updated as required.

and the packages in that repository appear as normal packages for them to select. When the author publishes a new version of their package it’ll appear as an update in all users package managers.

So easy.

These days, with CI, ya berge your patch and the fix is built and sent to testing immediately, ready to be assessed for promotion, which then signs and pushes the artifact into the pipeline for synchronization and application everywhere.

Aside from the actual smarts to build a good package, the tooling makes every other part of is zero-friction.

that defeats the purpose of a package manager

I suspect you’re confusing the package manager with the supply chain. This should always be separate, lest we get some systemd-like spongiform blob with no ability to swap out and improve parts without discarding the whole.

Unless you’re Lennart, it’s a bad idea.

Well, that sounds really immature.

Heckling introduces stress, providing incentive for improvement if the misbehaving member has that potential; otherwise shunning.

some aspects of the ecosystem seem to have not been thought out

Absolutely. But this is a natural effect of ditching mentors and documentors more than 20 years ago – coders now have no idea in general how to do supply-chains right; nor why.

Just give the source away. Don’t package it at all (or at most, do so for your own distro). If your software is good enough, others will do the packaging for you.

As someone who’s developed and shipped software you may know, who’s worked in rel/eng, OS security, escalations (we research the fix for the sploit and build the artifact for the update pipeline; everyone calls it something else) before being just an admin to manage hordes of machines; with the knowledge gained in every post I’ve ever held, let me say:

THIS. ABSOLUTELY THIS.

If you are a great coder but suck at packaging or hate it, then don’t. You’d produce something sub-par anyway.

Let the knowledgeable enthusiastic obsessively-detailed people do it for you and you’ll be happier and so will they.