teajaygrey, 6 months ago to opensource

My favorite @librewolf issue:

https://codeberg.org/librewolf/issues/issues/770

"Add support for MacPorts #770"

"Since Homebrew is supported why not Macports too?"

Me: a MacPorts maintainer, "maybe because MacPorts actually builds things from source and Homebrew thinks its OK to just be a wrapper to installing a DMG?"

e.g. https://github.com/Homebrew/homebrew-cask/blob/56d6d85d58a73a2b481cd5d58216296dd4239e63/Casks/f/flightgear.rb

Bad example?

Well here's the Homebrew cask for LibreWolf itself:
https://github.com/Homebrew/homebrew-cask/blob/56d6d85d58a73a2b481cd5d58216296dd4239e63/Casks/l/librewolf.rb

Again it's just a wrapper to installing a DMG!

That's not building jack it.sh from source. I guess it does have a little smarts insomuch as it will determine if it is Intel or Apple Silicon (meanwhile, MacPorts still supports PPC/G4/G5/etc. vintage systems. Because: it actually BUILDS THINGS FROM SOURCE, it's not a precompiled binary distribution platform.).

What a bad joke Homebrew is.

Alas, LibreWolf's build instructions are uhhh, well they don't build on macOS, they cross compile from ???

I mean there are the not so convincing notes on building from source here:
https://codeberg.org/librewolf/source

But also linked from there is this:

https://gitlab.com/librewolf-community/browser/macos

Which reads: "Archived project! Repository and other project resources are read-only"

I sincerely have no idea how people on macOS build LibreWolf from source, from the project documentation itself. Homebrew, is of zero assistance, because Homebrew: also does not build LibreWolf from source.

#MacPorts #LibreWolf #OpenSource #SourceWashing #Homebrew #ApplesnCrapples