Add package to MacPorts

[eirnym]

Hi,

Could you please add your package to MacPorts as well?

[eirnym]

@j178 Thank you for tagging the issue. Here's initial Portfile file attached and some information how to publish and maintain it. GitHub doesn't allow to attach files without extensions, so I've added .txt (which must be removed on submission)

Notes about Portfile:

• Source tarball require 3 checksums to be specified: sha256, rmd160 and size (in bytes). This will ensure that file is not tampered in any way (even one checksum can be broken, it's impossible to break all of them at once).
• It's a good idea to put maintainer to yourself instead of openmaintainer.
• MacPorts allows to install packages offline, so Rust dependencies used are also specified in the Portfile under cargo.crates section. This section is produced by cargo2port tool. It produces long list of dependencies from Cargo.lock file.

Publishing and updating:

• MacPorts official ports repository: https://github.com/macports/macports-ports
• Publishing PR is required like this example
• Update PR is required to be like this example

In case you don't have macOS or don't have (or want to add) an output for pkgutil --pkg-info=com.apple.pkg.CLTools_Executables and sw_vers on macOS on GitHub actions, here's my output:

MacOS version 15.7.2
Command Line Tools: 26.1.0.0.1.1761104275

Feel free to contact me if you have any further questions.

Portfile.txt

[j178]

Thanks for your detailed help! I have one question, does MacPorts require manually creating each update? That might create some maintenance burden. It would be really helpful if it could automatically create new update PRs like Homebrew does! :)

[eirnym]

There's some automation and … no there isn't. There's too many ports updated daily, so I believe that there's some better tools out there than seaport mentioned below.

Alternatively to solution I've wrote below, leave openmaintainer and ask this question in a PR. Please, CC me to that question please as I'm interested in that as well. This would be an easiest solution.

For automation there's currently a tool published in MacPorts named seaport. it's a bit old (2 years without any changes) and doesn't support new additions like cargo.crates section. This too is universal and basically run port command to upgrade things.

As you have a simple app without quirks, I'd created a simple template based on file I proposed to fill in version, checksums and dependencies based on source files to download. And with that result file then created/updated a PR to MacPorts. All of this can be done automatically from GitHub action

[j178]

macports/macports-ports#30165