Opened 4 years ago

Closed 4 years ago

#52110 closed update (fixed)

nodejs4 @4.4.7 update to 4.5.0

Reported by: l2dy (Zero King) Owned by: ci42
Priority: Normal Milestone:
Component: ports Version: 2.3.4
Keywords: Cc: herrbischoff (Marcel Bischoff)
Port: nodejs4

Description


Change History (10)

comment:1 Changed 4 years ago by ci42

Owner: changed from macports-tickets@… to ciserlohn@…

In the future please Cc the port maintainer(s) (port info --maintainers nodejs4).

comment:2 Changed 4 years ago by herrbischoff (Marcel Bischoff)

Yes, would be great to have a current LTS version.

comment:3 Changed 4 years ago by herrbischoff (Marcel Bischoff)

Cc: marcel@… added

Cc Me!

comment:4 Changed 4 years ago by l2dy (Zero King)

2016-09-27, Version 4.6.0 'Argon' (LTS), @rvagg

This is a security release. All Node.js users should consult the security release summary at https://nodejs.org/en/blog/vulnerability/september-2016-security-releases/ for details on patched vulnerabilities.

comment:5 Changed 4 years ago by herrbischoff (Marcel Bischoff)

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?

I'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?

Last edited 4 years ago by herrbischoff (Marcel Bischoff) (previous) (diff)

comment:6 in reply to:  1 Changed 4 years ago by herrbischoff (Marcel Bischoff)

Replying to ciserlohn@…:

In the future please Cc the port maintainer(s) (port info --maintainers nodejs4).

In the past 6 weeks your only action was to ask OP to include the port maintainers' address. According to https://guide.macports.org/#project.update-policies.abandonment this port could be considered abandoned.

comment:7 Changed 4 years ago by mf2k (Frank Schima)

Macports is switching to Github. There is currently a discussion about it on the Macports Developers mailing list. That is where you should bring up your issues with Macports, not this ticket where very few people will see it.

comment:8 Changed 4 years ago by herrbischoff (Marcel Bischoff)

Thanks for the nod in the right direction! I have just subscribed to the list and will direct my questions there.

comment:9 Changed 4 years ago by gallafent

Looks as if 4.6.0 has appeared in MacPorts so I'm guessing this ticket can be closed! It doesn't build for me mind you … and I am about to open a ticket to that effect!

comment:10 Changed 4 years ago by larryv (Lawrence Velázquez)

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.