[MacPorts] #54167: Gimp staging fails: expects lbzip2; uses wrong `touch`, found in node_modules

MacPorts noreply at macports.org
Sun May 14 02:38:46 UTC 2017


#54167: Gimp staging fails: expects lbzip2; uses wrong `touch`, found in
node_modules
------------------------------+-------------------
  Reporter:  paxperscientiam  |      Owner:
      Type:  defect           |     Status:  new
  Priority:  Normal           |  Milestone:
 Component:  ports            |    Version:  2.4.1
Resolution:                   |   Keywords:
      Port:  gimp, npm2       |
------------------------------+-------------------

Comment (by paxperscientiam):

 > This looks like two entirely separate issues. The first one is the use
 of lbzip2. MacPorts uses lbzip2 if available, but should fall back to
 bzip2 normally. I don't know why it did not work in this case...

 I wish I knew! I just ran `port installed bzip2` and got back ` bzip2
 @1.0.6_0 (active)`; so, I do have it installed.


 I checked `nodejs7` for notes, but there are none. `npm4` does, however,
 have notes.

 npm4 has the following notes:
 >It is not recommended to install packages globally. But if you do so
 please be aware that they won't get cleaned up when you deactivate or
 uninstall npm4. Globally installed packages will remain in
 /opt/local/lib/node_modules/ until you manually delete them.

 So, not recommended. Fine, but that's certainly not strong enough nor
 clear enough language. Is the reference to '/opt/local/lib/node_modules/'
 hardcoded, or is it programmatically generated based on some config
 variable?


 I just installed a node module and it spits out this:
 `/opt/local/bin/rollup -> /opt/local/lib/node_modules/rollup/bin/rollup`

 So, something is "mapping"
 ${PREFIX}/lib/node_modules/module/bin/executable to
 ${PREFIX}/bin/executable. I'm not sure what is doing this.

--
Ticket URL: <https://trac.macports.org/ticket/54167#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list