This repository has been archived by the owner on Jun 5, 2020. It is now read-only.
Update node-ffi for 0.12 compatibility #2
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
node-ffi prior to v1.3 doesn't build with node 0.12 See node-ffi/node-ffi#187
To verify that there's actually compatiblity with node 0.12 The addition of `sudo: false` allows travis to use a different VM, that starts much faster
cjohansen
added a commit
that referenced
this pull request
Jul 10, 2015
Update node-ffi for 0.12 compatibility
|
👍 Maybe @dwittner can publish? |
|
@mroderick, i just released version 0.1.5 of |
|
@dwittner thanks! I have confirmed that buster now installs correctly under |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
node-ffiprior to1.3doesn't build withnode@0.12See node-ffi/node-ffi#187
This means that
buster-cidoesn't build fornode@0.12, and in turn thatbusterdoesn't build fornode@0.12.Once this gets merged and published, we can create PRs for
buster-ciandbuster, and then finally publish an update tobusterthat will allow it to be used undernode@0.12