グレェ「grey」 says:
3 days ago at 11:30 pm
Good to know. Albeit, I tend to have a preference for MacPorts, mostly because jkh founded it, back when it was DarwinPorts, and when he was at Apple, and because FreeBSD's ports tree is still pretty darned decent, so Darwin/MacPorts kinda one-upped their legacy ever so slightly.

Homebrew always felt very NIH (Not Invented Here) syndrome, and way too "new cool buzzword" ruby-esque. For the sorts of people who dig Docker, and Kubernetes, and AWS and DevOps, instead of bare metal hardware and "ops, the dev is redundant, because if you couldn't code, you should never have been in ops or in wheel/sudoers/Enterprise Admins/etc. in the first place."

Albeit, maybe because I was introduced to Ruby via Why's Poignant Guide, I could never take it seriously. That, and the fact that it didn't support Japanese friendly encodings, even though it was written by a Japanese developer, was always a very WTF. For reference, EUC, JIS and Shift-JIS are older than UTF-8. Ruby was invented in 1995. UTF-8 was invented in 1992. Something, to me at least, SCREAMED, that it was amateur hour, as well as everyone who used it. Still, pretty entertaining as a joke, sorta like LOLCODE, or brainfuck, but way less funny when you realized that people took the joke too far. In Ruby's defense, it did eventually get UTF-8 support at least.

Not to suggest that MacPorts is without its flaws. After reading jwz's tirade on Let's Encrypt, I noticed that MacPort's LibreSSL port was pretty far behind, discovered an even further behind libressl-devel (wtfh?) and a devel/libretls (WTFH WTFH WTFH). Regardless, after I didn't receive a reply from the port maintainer for a week, I opened a Trac ticket, and submitted some diffs. I was told to submit a GitHub pull request (Why? Really. Why is Trac insufficient? Why do they insist on using a tool owned by Microsoft, which supports ICE amongst other 'Murican branches of fascism?). Anyway, reservations about GitHub aside, I futzed around with the gh CLI tools, clone a tree of macports (because, apparently I can't just clone /security/libressl it has to be the entire friggin' ports repo), added my modified Portfile with the diffs from Trac, and submitted a PR.

I received an e-mail, from someone entirely unclued to the Trac ticket, apparently, that the commit message was non-standard. In their defense, maybe it was. In my defense: I do not have commit access, the port in MacPorts is almost a year old, and knowing that OpenBSD 7.0 was about to be released, I figured that 3.4.0 (which didn't have the changes merged from 3.3.5) was about to get replaced by something newer and mentioned as much in a disclaimer in the commit message.

Sure enough, days later, OpenBSD 7.0 was released, their tree was unfrozen, and LibreSSL 3.4.1 was released.

So, I backed out the PR.

I updated the Trac ticket, submitted new diffs for 3.4.1.

The port maintainer, still has not replied. (He apparently, has a day job, at Apple. Must be nice to get paid. Though, Apple's LibreSSL in 11.16 macOS Big Sur is 2.8.3, which was released in 2018 and definitely awfully long in the tooth, so.... I hope he doesn't maintain that too, though it might explain some things.)

The pedantic hater on GitHub replied though! Not with anything helpful mind you.