README: add MacPorts install info

[herbygillot]

Add information on installing rare using MacPorts

Port page for rare is here

[netlify]

✔️ Deploy Preview for raredocs ready!

🔨 Explore the source changes: 1ff91cf

🔍 Inspect the deploy log: https://app.netlify.com/sites/raredocs/deploys/6123f7f2e622010007cb6619

😎 Browse the preview: https://deploy-preview-58--raredocs.netlify.app/

[zix99]

Howdy! Thanks for the contribution to both the repo and macports.

I'm more familiar with homebrew rather than macports.. is there somewhere I can verify that the code from this repo is published unaltered there? Happy to include it in the readme/docs if so (Though I might ask to stick it under a separate Community Contributed section since it's not maintained by me)

Thanks!

[herbygillot]

Howdy! Thanks for the contribution to both the repo and macports.

I'm more familiar with homebrew rather than macports.. is there somewhere I can verify that the code from this repo is published unaltered there? Happy to include it in the readme/docs if so (Though I might ask to stick it under a separate Community Contributed section since it's not maintained by me)

Thanks!

Hey @zix99, no worries. Here's rare's port page. If you click the Details button, then click the GitHub link, you'll be taken to the Portfile for rare.

The Portfile tells MacPorts how to build a particular piece of software. rare's Portfile pulls the source from the right branch in this repository via the go.setup line:

go.setup            github.com/zix99/rare 0.2.0

Normally a Portfile includes a set of checksums to verify that what has been pulled matches what is expected, but since we're building via goreleaser, we pull via git instead of downloading a source tarball (fetch.type git).

After that goreleaser does its thing (build.cmd, build.pre_args & build.args) and builds rare, which MacPorts then packages and pushes to MacPorts distribution mirrors.

The specified maintainer is usually responsible for keeping the port up to date, but anyone is welcome to open a pull request updating the version (which is reviewed by maintainers and project admins before being committed).

And yes, this certainly makes sense falling under the Community Contributed section.

[zix99]

Thanks, appreciate the explanation. Will merge and reorg the docs a bit.

[herbygillot]

Thanks @zix99