On 2016-11-01 05:54, Mojca Miklavec wrote:
> I can imagine a newbie trying to navigate to the page and thinking
> that installation of Homebrew is necessary for making that software
> work, just to screw up the rest of MacPorts. An additional problem
> might be that whenever users have a problem with the software and file
> a bug report, they might get an equally annoying answer saying
> "Install Homebrew, I don't support MP". I had a problem with one
> particular project in the past that a typical answer to any bug report
> I filed was "stop using MacPorts, it's obviously broken" when in 90%
> of the cases it was their bug that just showed up when using certain
> newer dependencies or a particular set of configure flags they never
> tested.

You see these kind of messages on many software homepages on the web,
because the Homebrew crowd has to spew it everywhere. Nobody should
think Homebrew is required because of them.

By adding hub to instructions, we never send people to their homepage,
so they will not even see this message.

> I'm with Ryan in this case. We don't prevent anyone from using this
> software if they choose to, I just don't see the point of advertising
> software whose maintainer decided to go against MP.

This argument is just nonsense. I am not going to stop using vim just
because upstream decided to mention Homebrew (and only Homebrew) in its
README_mac [1].

I do not see valid reasons not to use hub.


[1] https://github.com/vim/vim/blob/master/READMEdir/README_mac.txt
macports-dev mailing list

Reply via email to