macports-ports

In my experience, you want "emacs-app", which is just upstream emacs compiled with Aqua support (https://github.com/macports/macports-ports/blob/81b99bcf7c59...) to avoid going through XQuartz.

You're welcome to add me as a co-maintainer on this if you submit it to macports/macports-ports: {macports.halostatue.ca:austin @halostatue} I maintain https://github.com/macports/macports-ports/blob/master/sysut... amongst other things regularly.

I've made a private MacPorts port[1]; if I find that I use it frequently enough, I might contribute it to the main MacPorts port repo[2]. One thing that's missing from my perspective (and this is probably true for Homebrew packaging as well, but I don't do that) is Git tags / GitHub releases associated with your Cargo releases. I can work around it for now by using an explicit release (`9ccd9bf53f9a309ccda42b5c17e9c1056493fb90` is what I'm assuming was your 0.1.0 release point). I've also assumed that npm10 is sufficient (which currently installs node22 on MacPorts). [1] https://github.com/halostatue/ports [2] https://github.com/macports/macports-ports [3] https://github.com/halostatue/ports/commit/e7331a7fcae362b0d...

> Can you name an important software written in Tcl or Tk? MacPorts[0] uses Tcl significantly. EDIT: The expect[1] command also uses Tcl and has a variant which uses Tk. 0 - https://github.com/macports/macports-ports 1 - https://man.freebsd.org/cgi/man.cgi?query=expect&apropos=0&s...

>> this immensely flexible and versatile language > I would be interested to know if anyone ever built anything non-trivial that didn't turn into a complete mess due to TCL's general type-flimsyness and "everything is a string" philosophy. Both MacPorts CLI client[0] and ports tree[0] have used it successfully for many years. Regarding: "everything is a string" philosophy That can be said for the vast majority of Unix-like OS user-space programs. 0 - https://github.com/macports/macports-base 1 - https://github.com/macports/macports-ports

I was curious if it was just some kind of horrific backlog but there didn't seem to be an oppressive number of PRs open, although it seems the new submissions drag their feet quite a bit https://github.com/macports/macports-ports/pulls?q=is%3Apr+i... Also, it seems there is currently one in progress to drop the "6" qualifier on the ffmpeg binaries <https://github.com/macports/macports-ports/pull/23315/files> so it'll be fascinating to see if any new ffmpeg7 then subsequently puts the "7" back, beginning the cycle again

Similarly if you're using MacPorts, make sure to sync and upgrade xz if you have it installed. 5.6.1 was available for a few days and just rolled back ~20 minutes ago: https://github.com/macports/macports-ports/commit/a1388aee09...

Another anecdote: the MacPorts package definition files [1] are actually TCL programs. MacPorts itself is built on TCL [2] [1] Example portfile: https://github.com/macports/macports-ports/blob/master/shell... [2] Macports source: https://github.com/macports/macports-base/tree/release-2.7/s...

> Godot - doesn't work Godot has been working well for me under Rosetta (though just a small 2D project using GDScript). Godot 3.2.3 actually supports Apple Silicon[1] although there's no binary build just yet. I've recently submit a patch to MacPorts to enable native Apple Silicon[2] and have been using it since without any issues (so far). [1]: https://docs.godotengine.org/en/stable/development/compiling... [2]: https://github.com/macports/macports-ports/pull/9552

MacPorts' Portfile[1], maybe? Portfile is being evaluated entirely within interp[2] with only few functions exposed inside the environment [1]: https://github.com/macports/macports-ports/blob/master/lang/... [2]: https://www.tcl.tk/man/tcl8.4/TclCmd/interp.htm

mas is independent of Homebrew and available on MacPorts: https://github.com/macports/macports-ports/blob/master/sysut.... There's discussion on the mailing list on whether MacPorts should have a sort of "caskroom" type thing–currently it tries to avoid this except in cases where it's impractical to build from source (e.g. Java).

It's not dead! [1] I use it daily, and it's working just fine. For example, check out the (centralized) list [2] of Ports files that define the packages. You can see it's pretty lively But your perception that it's dead is certainly symptomatic of an issue for the project. [1] yes yes Monty Python [2] https://github.com/macports/macports-ports

I thought so too at first, but it's not! It's maintained relatively actively (https://github.com/macports/macports-ports/commits/master), so I think this perspective is mostly just a result of Homebrew having better marketing/more people using it.

It looks like the MacPorts version of shellcheck is substantially out-of-date[1]. `brew info shellcheck` shows just three (build-time) dependencies: cabal-install, ghc, and pandoc. [1]: https://github.com/macports/macports-ports/commits/master/de...