Re:macOS deprecating scripting language runtimes, including ...
by jarcane on Thursday June 06, 2019 @01:56AM
(#20111966)
Homebrew is not the only package provider for MacOS.
[ Parent
| on HN ]
Re:macOS deprecating scripting language runtimes, including ...
by reikonomusha on Thursday June 06, 2019 @01:57AM
(#20111977)
Would Apple be in the wrong simply being opinionated about using Homebrew?
Re:macOS deprecating scripting language runtimes, including ...
by mschuster91 on Thursday June 06, 2019 @02:44AM
(#20112158)
Yes, because Homebrew's practice of installing packages runs contrary to the requirements of a multi-user system.
Re:macOS deprecating scripting language runtimes, including ...
by wyufro on Thursday June 06, 2019 @03:38AM
(#20112367)
MacPorts is sponsored by Apple, or at least used to be.
Re:macOS deprecating scripting language runtimes, including ...
by raimue on Thursday June 06, 2019 @05:06AM
(#20112801)
MacPorts was originally started as DarwinPorts as part of the OpenDarwin initiative at Apple [1]. Apple continued to sponsor MacPorts by providing hosting of website, repository, and build servers at Mac OS forge [2] until it closed back in 2016. The project then moved to GitHub and their own servers.
Re:macOS deprecating scripting language runtimes, including ...
by anentropic on Thursday June 06, 2019 @04:56AM
(#20112762)
TBH it's weird they haven't built their own
Re:macOS deprecating scripting language runtimes, including ...
by hasahmed on Thursday June 06, 2019 @02:03AM
(#20111999)
Yes
Re:macOS deprecating scripting language runtimes, including ...
by csomar on Thursday June 06, 2019 @02:45AM
(#20112163)
I'm not sure why you are getting downvoted. I'd not like it if Apple will opinion-ate and make any package manager a default.
Package managers are for software developers. They are comfortable installing them on their own.