#48827 closed update (fixed)
nodejs: update to 4.0.0
| Reported by: | felipou (Felipe Machado) | Owned by: | ci42 |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | haspatch | Cc: | ryandesign (Ryan Carsten Schmidt), dliessi (Davide Liessi), pe8ter@…, tapplekos@…, m74z00219@… |
| Port: | nodejs |
Description
Nodejs merged with iojs, and version 4.0.0 was released this week: https://github.com/nodejs/node/blob/v4.0.0/CHANGELOG.md
I believe many people will need to stick to the 0.12.x branch for some time, so I think it would be nice if macports kept both versions for a while (just a suggestion).
Anyway, I'm creating this ticket to request that nodejs v4.0.0 be made available on macports.
Thanks!
Attachments (7)
Change History (27)
comment:1 Changed 9 years ago by ci42
| Keywords: | nodejs iojs removed |
|---|---|
| Owner: | changed from macports-tickets@… to ciserlohn@… |
| Port: | iojs added |
| Type: | request → update |
comment:4 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
| Port: | iojs removed |
|---|---|
| Summary: | Nodejs 4.0.0 → nodejs: update to 4.0.0 |
| Version: | 2.3.3 |
comment:6 Changed 9 years ago by seanfarley (Sean Farley)
Hmm, I actually need this for work. I can post some patches here tomorrow for review if that helps.
Changed 9 years ago by seanfarley (Sean Farley)
| Attachment: | nodejs.patch added |
|---|
Update nodejs to 4.0.0
Changed 9 years ago by seanfarley (Sean Farley)
| Attachment: | iojs.patch added |
|---|
Deprecate iojs with nodejs
comment:7 Changed 9 years ago by seanfarley (Sean Farley)
Ok, I just attached the patches. Let me know if there's something else I can test to verify this working.
comment:8 Changed 9 years ago by seanfarley (Sean Farley)
| Keywords: | haspatch added |
|---|
comment:13 follow-up: 14 Changed 9 years ago by seanfarley (Sean Farley)
I'll see about the update to 4.1.1 today. Any objections to me pushing this?
comment:14 Changed 9 years ago by ci42
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Replying to sean@…:
I'll see about the update to 4.1.1 today. Any objections to me pushing this?
Thanks for the patches. Please use the nodejs-devel port for now which I just updated to 4.1.1. I'd like to keep the nodejs port at v0.12.7 for a while to ease the transition.
npm will be updated soon - I'm currently testing v3.3.4. The iojs port will be removed when the nodejs port is at 4.x and nodejs-devel at 5.x.
Changed 9 years ago by seanfarley (Sean Farley)
| Attachment: | nodejs-github.patch added |
|---|
use github port group
Changed 9 years ago by seanfarley (Sean Farley)
| Attachment: | nodejs-devel-subport.patch added |
|---|
make nodejs-devel a subport of nodejs
comment:15 Changed 9 years ago by seanfarley (Sean Farley)
By the way, I would suggest using the github port group because it would simplify some of the code. Also, I have a patch that makes nodejs-devel a subport since both files are basically the same, so we can cut down on code duplication. Having it use the github port group would help with making the devel version easy to roll out.
Changed 9 years ago by seanfarley (Sean Farley)
| Attachment: | nodejs-devel-rebased-github.patch added |
|---|
rebased nodejs-devel using github port group so it applies to trunk
Changed 9 years ago by seanfarley (Sean Farley)
| Attachment: | npm-3.3.4.patch added |
|---|
update npm to 3.3.4
comment:16 Changed 9 years ago by seanfarley (Sean Farley)
I uploaded two patches that apply to trunk now; hopefully that will help you update npm to 3.3.4 and consider using the github portgroup.
comment:17 Changed 9 years ago by pe8ter@…
Is this talk of using the "github port group" meant meant as a suggestion for the port maintainers or is this a something for me, the enduser, to be concerned with?
comment:18 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
It's a suggestion for the maintainer.
comment:19 follow-up: 20 Changed 8 years ago by rsternagel@…
Is there a chance to get npm v3 soon? In my mind it makes sense to have a npm2 (e.g. "npm") and a npm3 (e.g. "npm-devel") port. At least for some time. However, @ciserlohn thanks for the regular updates!
comment:20 Changed 8 years ago by ci42
Replying to rsternagel@…:
Is there a chance to get npm v3 soon? In my mind it makes sense to have a npm2 (e.g. "npm") and a npm3 (e.g. "npm-devel") port. At least for some time. However, @ciserlohn thanks for the regular updates!
I added a new npm-devel port which is now at version 3.3.9.
In the future please Cc the port maintainer (
port info --maintainer nodejs) and don't use arbritary keywords (see DraftKeywordGuidelines)