Context Navigation

← Previous Ticket
Next Ticket →

#39440 closed defect (wontfix)

nodejs: upgrading from @0.8.15 to @0.10.11 removes node-waf

Reported by:	cooljeanius (Eric Gallager)	Owned by:	macports-tickets@…
Priority:	Normal	Milestone:
Component:	ports	Version:	2.1.3
Keywords:		Cc:	ci42
Port:	nodejs

Description

I recently upgraded my nodejs installation, and on upgrading, it removed these files:

--->  Deactivating nodejs @0.8.15_0+python27+ssl
DEBUG: deactivating file: /opt/local/share/man/man1/node.1.gz
DEBUG: /opt/local/share/man/man1 is not empty
DEBUG: /opt/local/share/man is not empty
DEBUG: deactivating file: /opt/local/share/doc/nodejs/README.md
DEBUG: deactivating file: /opt/local/share/doc/nodejs/LICENSE
DEBUG: deactivating file: /opt/local/share/doc/nodejs/ChangeLog
DEBUG: deactivating file: /opt/local/share/doc/nodejs/AUTHORS
DEBUG: deactivating directory: /opt/local/share/doc/nodejs
DEBUG: /opt/local/share/doc is not empty
DEBUG: /opt/local/share is not empty
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/py3kfixes.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/pproc.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/ansiterm.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/__init__.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Utils.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/xlcxx.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/xlc.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/winres.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/unittestw.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/suncxx.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/suncc.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/python.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/preproc.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/osx.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/node_addon.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/nasm.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/misc.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/libtool.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/intltool.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/icpc.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/icc.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/gxx.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/gob2.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/gnu_dirs.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/gdc.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/gcc.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/gas.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/dmd.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/d.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/cxx.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/config_c.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/compiler_d.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/compiler_cxx.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/compiler_cc.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/ccroot.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/cc.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/ar.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Tools/__init__.py
DEBUG: deactivating directory: /opt/local/lib/node/wafadmin/Tools
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/TaskGen.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Task.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Scripting.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Runner.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Options.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Node.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Logs.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Environment.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Constants.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Configure.py
DEBUG: deactivating file: /opt/local/lib/node/wafadmin/Build.py
DEBUG: deactivating directory: /opt/local/lib/node/wafadmin
DEBUG: deactivating directory: /opt/local/lib/node
DEBUG: deactivating file: /opt/local/lib/dtrace/node.d
DEBUG: deactivating directory: /opt/local/lib/dtrace
DEBUG: /opt/local/lib is not empty
DEBUG: deactivating file: /opt/local/include/node/v8stdint.h
DEBUG: deactivating file: /opt/local/include/node/v8.h
DEBUG: deactivating file: /opt/local/include/node/v8-testing.h
DEBUG: deactivating file: /opt/local/include/node/v8-profiler.h
DEBUG: deactivating file: /opt/local/include/node/v8-preparser.h
DEBUG: deactivating file: /opt/local/include/node/v8-debug.h
DEBUG: deactivating file: /opt/local/include/node/uv.h
DEBUG: deactivating file: /opt/local/include/node/uv-private/uv-win.h
DEBUG: deactivating file: /opt/local/include/node/uv-private/uv-unix.h
DEBUG: deactivating file: /opt/local/include/node/uv-private/tree.h
DEBUG: deactivating file: /opt/local/include/node/uv-private/ngx-queue.h
DEBUG: deactivating file: /opt/local/include/node/uv-private/ev.h
DEBUG: deactivating file: /opt/local/include/node/uv-private/eio.h
DEBUG: deactivating directory: /opt/local/include/node/uv-private
DEBUG: deactivating file: /opt/local/include/node/node_version.h
DEBUG: deactivating file: /opt/local/include/node/node_object_wrap.h
DEBUG: deactivating file: /opt/local/include/node/node_buffer.h
DEBUG: deactivating file: /opt/local/include/node/node.h
DEBUG: deactivating file: /opt/local/include/node/ev-emul.h
DEBUG: deactivating file: /opt/local/include/node/eio-emul.h
DEBUG: deactivating file: /opt/local/include/node/ares_version.h
DEBUG: deactivating file: /opt/local/include/node/ares.h
DEBUG: deactivating directory: /opt/local/include/node
DEBUG: /opt/local/include is not empty
DEBUG: deactivating file: /opt/local/bin/node-waf
DEBUG: deactivating file: /opt/local/bin/node
DEBUG: /opt/local/bin is not empty
DEBUG: /opt/local is not empty
DEBUG: /opt is not empty
DEBUG: / is not empty
DEBUG: Executing org.macports.main (nodejs)
DEBUG: clean phase started at Fri Jun 14 17:08:36 EDT 2013
--->  Cleaning nodejs

Now it contains:

Local-Admins-MacBook-Pro:nodetcl ericgallager$ port contents nodejs
Port nodejs contains:
  /opt/local/bin/node
  /opt/local/include/node/ares.h
  /opt/local/include/node/ares_version.h
  /opt/local/include/node/node.h
  /opt/local/include/node/node_buffer.h
  /opt/local/include/node/node_object_wrap.h
  /opt/local/include/node/node_version.h
  /opt/local/include/node/uv-private/ngx-queue.h
  /opt/local/include/node/uv-private/tree.h
  /opt/local/include/node/uv-private/uv-unix.h
  /opt/local/include/node/uv-private/uv-win.h
  /opt/local/include/node/uv.h
  /opt/local/include/node/v8-debug.h
  /opt/local/include/node/v8-preparser.h
  /opt/local/include/node/v8-profiler.h
  /opt/local/include/node/v8-testing.h
  /opt/local/include/node/v8.h
  /opt/local/include/node/v8stdint.h
  /opt/local/lib/dtrace/node.d
  /opt/local/share/doc/nodejs/AUTHORS
  /opt/local/share/doc/nodejs/ChangeLog
  /opt/local/share/doc/nodejs/LICENSE
  /opt/local/share/doc/nodejs/README.md
  /opt/local/share/man/man1/node.1.gz

Was the node-waf executable supposed to have been removed like that? I need it to configure a package I'm working on porting: https://github.com/bovine/nodetcl

Change History (6)

comment:1 follow-up: 2 Changed 11 years ago by larryv (Lawrence Velázquez)

Resolution:	→ wontfix
Status:	new → closed

Upstream removed it from unstable 0.9.1 last year.

https://github.com/joyent/node/blob/v0.9.1/ChangeLog#L11

comment:2 in reply to: 1 ; follow-up: 3 Changed 11 years ago by cooljeanius (Eric Gallager)

Replying to larryv@…:

Upstream removed it from unstable 0.9.1 last year.

https://github.com/joyent/node/blob/v0.9.1/ChangeLog#L11

Hm, darn. So could there be a separate nodejs8 port or something for projects that still need node-waf?

comment:3 in reply to: 2 ; follow-up: 4 Changed 11 years ago by larryv (Lawrence Velázquez)

Replying to egall@…:

Hm, darn. So could there be a separate nodejs8 port or something for projects that still need node-waf?

That seems like major overkill. Do we even have any ports that require node-waf?

And it looks like projects should be moving to node-gyp anyway.

comment:4 in reply to: 3 ; follow-up: 5 Changed 11 years ago by cooljeanius (Eric Gallager)

Replying to larryv@…:

And it looks like projects should be moving to node-gyp anyway.

ok, so how about a port for node-gyp then? It doesn't look like there currently is one:

Local-Admins-MacBook-Pro:~ root# port search gyp
No match for gyp found

Fink has a gyp package btw: http://fink.cvs.sourceforge.net/fink/dists/10.4/stable/main/finkinfo/libs/pythonmods/gyp-py.info?view=markup

comment:5 in reply to: 4 ; follow-up: 6 Changed 11 years ago by ci42

Replying to egall@…:

Replying to larryv@…:

And it looks like projects should be moving to node-gyp anyway.

ok, so how about a port for node-gyp then? It doesn't look like there currently is one:
Local-Admins-MacBook-Pro:~ root# port search gyp
No match for gyp found
Fink has a gyp package btw: http://fink.cvs.sourceforge.net/fink/dists/10.4/stable/main/finkinfo/libs/pythonmods/gyp-py.info?view=markup

node-gyp is available through npm:

$ sudo port install npm

(...)

$ npm search node-gyp
npm http GET https://registry.npmjs.org/-/all/since?stale=update_after&startkey=1371365984238
npm http 200 https://registry.npmjs.org/-/all/since?stale=update_after&startkey=1371365984238
NAME      DESCRIPTION                      AUTHOR                DATE              VERSION KEYWORDS
node-gyp  Node.js native addon build tool  =TooTallNate =tootallnate 2013-06-05 23:02 0.10.0  native addon module c c++ bindings gyp
$

comment:6 in reply to: 5 Changed 11 years ago by cooljeanius (Eric Gallager)

Replying to ciserlohn@…:

node-gyp is available through npm:

$ sudo port install npm

(...)

$ npm search node-gyp
npm http GET https://registry.npmjs.org/-/all/since?stale=update_after&startkey=1371365984238
npm http 200 https://registry.npmjs.org/-/all/since?stale=update_after&startkey=1371365984238
NAME      DESCRIPTION                      AUTHOR                DATE              VERSION KEYWORDS
node-gyp  Node.js native addon build tool  =TooTallNate =tootallnate 2013-06-05 23:02 0.10.0  native addon module c c++ bindings gyp
$

OK, that could work for building manually, but how would I go about calling that from a portfile? I would imagine it would be a bad idea to call npm from a portfile, as then the files it installs would be untracked by MacPorts. We already have ports for perl modules, python eggs, ruby gems, cabal and opam packages, and probably some things from a few other language-specific package managers that I'm forgetting. Couldn't we start carrying ports for npm modules, too?

Note: See TracTickets for help on using tickets.

Download in other formats: