diff options
author | Jean-Marie LEMETAYER <jean-marie.lemetayer@savoirfairelinux.com> | 2019-05-17 17:14:09 +0200 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2019-05-21 12:56:33 +0100 |
commit | a34d0d539e5fdf341541fb628652d22289e80512 (patch) | |
tree | 66c1cccdd83020ef44262aa9563065a8931fc2f3 /meta-selftest/wic | |
parent | eecba41822e86b69ebdb9cbc8fbfd512ad9a47d7 (diff) | |
download | poky-a34d0d539e5fdf341541fb628652d22289e80512.tar.gz |
npm: fix node and npm default directory conflict
Fixes [YOCTO #13349]
When dealing with node modules which have declared "bin" files [1], npm
will create a link in '/usr/bin' with a relative link to
'../lib/node_modules/<module bin file>'.
The commits e9270af4296ce2af292059617a717e42fc17425c and
2713d9bcc39c712ef34003ce8424416441be558e explicitely use
'/usr/lib/node/' as install directory, but does not care about the "bin"
symbolic linked files.
In order to keep valid links, and to keep it as simple as possible, the
path '/usr/lib/node_modules/' is used as install directory for npm. And
a symbolic link is created to have a valid '/usr/lib/node/' path, needed
for node.
[1]: https://docs.npmjs.com/files/package.json#bin
(From OE-Core rev: 2d72007deea7ed529f82b8a6e67e2715dd0a0dca)
Signed-off-by: Jean-Marie LEMETAYER <jean-marie.lemetayer@savoirfairelinux.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta-selftest/wic')
0 files changed, 0 insertions, 0 deletions