Closed justmoon closed 8 years ago
Thanks a bunch for this PR. I'll see if I can get it merged.
bump What's the status on this?
master is now 1.1.15, mostly based on the work here
and npm published with builds for linux + mac
@dominictarr dang, should we revert?
aka, unpublish this and wait for a fix
yes I think so, I already pinned to previous version in chloride, and submitted fix.
its unpublished now. when a new upstream release is made with your PRs i'll build + release a new version here.
Upstream is now merged and released: https://github.com/paixaop/node-sodium/pull/89
@mafintosh @dominictarr Since the upstream fix has been merged and released in 2.0.0/2.0.1, we should be ready to try this again.
👍
@mafintosh Could you give this another go? Should be ok to pull in upstream now!
@justmoon i'm a swamped atm but i can add you as owner if you want to give it a try?
@mafintosh Sure, I'd be happy to.
Time for the bimonthly poke!
cc/ @mafintosh
@justmoon just added you. sorry for the delay. i'm personally just using https://github.com/mafintosh/sodium-native now
Upstream has advanced quite a bit (
1.0.22 -> 1.1.12
) - dunno how useful this PR is, but I figured some kind of PR is better than showing up empty handed on Twitter. The whole thing is just 9e0d720 on top of the upstream tag1.1.12
.Main issue was dealing with the changes to the
preinstall
andinstall
targets in upstream'spackage.json
. Since prebuild's--preinstall
option doesn't support arguments, I used&&
and||
which seems to work, but... not convinced this won't break in some situations.Successfully tested
npm run prebuild
on Linux x64 and Win32 x64.