[MacPorts] #39440: nodejs: upgrading from @0.8.15 to @0.10.11 removes node-waf

[MacPorts]

#39440: nodejs: upgrading from @0.8.15 to @0.10.11 removes node-waf
----------------------+--------------------------------
  Reporter:  egall@…  |      Owner:  macports-tickets@…
      Type:  defect   |     Status:  closed
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:  2.1.3
Resolution:  wontfix  |   Keywords:
      Port:  nodejs   |
----------------------+--------------------------------

Comment (by egall@…):

 Replying to [comment:5 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?

-- 
Ticket URL: <https://trac.macports.org/ticket/39440#comment:6>
MacPorts <http://www.macports.org/>
Ports system for OS X