Update build-osx.md

[atErik]

Adding instructions to use MacPorts pkg-mngr in macOS. Adding instructions to turn-off anti-privacy data-collection activities of Homebrew pkg-mngr.

[hebasto]

@atErik

Thank you for your contribution.

Adding instructions to turn-off anti-privacy data-collection activities of Homebrew pkg-mngr.

Concept ~0 about that as it looks out of this repo scope. Our docs should not duplicate 3rd-party software docs.

[jarolrod]

Thank you for your contribution!

I am NACK on this, our build docs are meant to provide guidance on building. They aren't meant to list every piece of information or iterate on all the possible ways that packages can be installed. The current instructions are easily adaptable to someone using macports as a package manager; so we don't have to duplicate information for that here.

[maflcko]

Closing for now due to controversy

[atErik]

@MarcoFalke & others , sorry to respond in late.

MacPorts pkg's name, and homebrew pkg's name, are not same,
they are not-duplicate pkg-names or duplicate commands,
and+so it takes time to find a MacPorts compatible pkg.

So i'm requesting to add macports pkg name lines, etc.

@hebasto , then we need to add the link to the Homebrew project that instructs on how to turn-off this data-collection activities : https://docs.brew.sh/Analytics

I'm neither in the group who will hide this by-default mass-scale data-collection violation by homebrew prj,
i'm nor in the group who will promote a product w/o notifying users about such data-collection practices/activities.

By not-including MacPorts info, devs in this prj have decided to discourage more use/adoption of MacPorts, and supporting homebrew only.

More info on who are turning this data-collection Analytics off : https://html.duckduckgo.com/html?q=brew%20analytics%20off
https://html.duckduckgo.com/html?q=criticism%20problems%20of%20homebrew%20analytics

or, Please allow me to create a small link in this page, to show another page (under this prj), where i can add these instructions on using MacPorts,
or, please create a linked page, add initial info from this request to there in new page,
then i or MacPorts user community can contribute further there, if needed.

[hebasto]

@atErik

@hebasto , then we need to add the link to the Homebrew project that instructs on how to turn-off this data-collection activities : https://docs.brew.sh/Analytics

Disagree. Ultimately, it could end with data-collection activities notes for OSes which are used to run Bitcoin Core.

By not-including MacPorts info, devs in this prj have decided to discourage more use/adoption of MacPorts, and supporting homebrew only.

We care about maintaining our build system with very restricted resources. Even supporting the only package manager for macOS is a decent maintenance burden. Also Homebrew is preinstalled on macOS images being used in our CI workflow.