Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#54168 - Split node-gyp into its own package
Attached to Project:
Community Packages
Opened by Chris Kitching (ckitching) - Tuesday, 23 May 2017, 16:51 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 23 May 2017, 23:43 GMT
Opened by Chris Kitching (ckitching) - Tuesday, 23 May 2017, 16:51 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 23 May 2017, 23:43 GMT
|
DetailsCurrently, the npm package bundles a (broken) node-gyp, and marks python2 as an optdepend to make it work:
https://www.archlinux.org/packages/community/any/npm/ Surely it'd be better to put node-gyp in a separate package which has a hard dependency on python2 and npm? |
This task depends upon