Changes between Version 2 and Version 3 of Ticket #52110, comment 5


Ignore:
Timestamp:
Oct 6, 2016, 1:03:34 PM (4 years ago)
Author:
herrbischoff (Marcel Bischoff)
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #52110, comment 5

    v2 v3  
    1 I'm currently considering dropping the use of MacPorts as this projects' track record regarding critical updates of major software tools is rather underwhelming.Furthermore, I'm asking myself what use it is to be a port maintainer when updates are not included in a timely manner. This ticket is six weeks old. Node.js 4.5.0 was released on 16-Aug-2016. If time and manpower is the problem, wouldn't it be better to move to a GitHub-based approach like Homebrew does? This way far more people would contribute. I like MacPorts' clean implementation far more than Homebrews'. But if I still cannot install for example {{{pandoc}}} because {{{ghc}}} still requires {{{llwm-3.5}}} which does not compile on Sierra: what good is a package manager that does not work reliably on the current platform it's designed for to work on?
     1I'm currently considering dropping the use of MacPorts as this projects' track record regarding critical updates of major software tools is rather underwhelming. Furthermore, I'm asking myself what use it is to be a port maintainer when updates are not included in a timely manner. This ticket is six weeks old. Node.js 4.5.0 was released on 16-Aug-2016. If time and manpower is the problem, wouldn't it be better to move to a GitHub-based approach like Homebrew does? This way far more people would contribute. I like MacPorts' clean implementation far more than Homebrews'. But if I still cannot install for example {{{pandoc}}} because {{{ghc}}} still requires {{{llwm-3.5}}} which does not compile on Sierra: what good is a package manager that does not work reliably on the current platform it's designed for to work on?
    22
    33I'd really like to hear from several sides about the why's and how's. I'm not sure where to ask this question as to get the broadest possible input. On GitHub I'd just open an issue. Should I do the same here?