2 ms·
One should bear in mind that it seems MacPorts takes a much more puritan approach to packaging than Homebrew, as this 18 month old ticket asking for awscli v2 (
by mdaniel 5y ago
One should bear in mind that it seems MacPorts takes a much more puritan approach to packaging than Homebrew, as this 18 month old ticket asking for awscli v2 (and its comment thread) shows: https://trac.macports.org/ticket/60452 https://trac.macports.org/ticket/60452
I didn't dig into the process for a user to add their own ports, or share new ports with a team, in order to more fully compare the two packagers, but that ticket stood out to me
- kergonath 5y agoI don’t get how that thread demonstrates what you say. It just looks like awscli 2 is a pain to package; what am I missing?
- mdaniel 5y agoWell, one will observe that brew manages to package it, without any similar stone throwing about the project's "hatred for pypi" or other meta commentary. It seems every project has *some* kind of quirk, but if the packaging system pays that cost once, then its users get "brew install awscli" instead of waiting 18 months for the AWS team to "see the error of their ways" or whatever one is expecting to change about that situation I apologize if "puritan" was too emotionally loaded of a word that hurt people's feelings -- I didn't think "strict" was the right word but maybe I should have used "opinionated?"
- Wowfunhappy 5y agoMy read of that ticket is it's a bunch of people saying "this looks hard, I don't want to do it." But if someone wrote a (good) pull request, I expect MacPorts would accept it. The thing about MacPorts is that it's a very community-driven project. Things happen when someone decides to go do them. (Individual maintainers are sometimes opinionated, but I wouldn't say they speak for the whole of MacPorts.)