Skip to content

Conversation

maclover7
Copy link
Contributor

@maclover7 maclover7 commented Aug 1, 2018

Beginning in nodejs/node@537a4ba,
deps/uv/include/uv-version.h moved to deps/uv/include/uv/version.h, so add
that as a possible path where libuv's version might be stored.

Refs: nodejs/node#21466


Unrelated note, but cc @Trott in case there are folks looking to get involved somewhere in Node, this is a low visibility with super high impact codebase (in JS) that could use some good refactoring. Happy to help mentor/review PRs if there are any takers...

Beginning in nodejs/node@537a4ba,
`deps/uv/include/uv-version.h` moved to `deps/uv/include/uv/version.h`, so add
that as a possible path where libuv's version might be stored.

Refs: nodejs/node#21466
@maclover7
Copy link
Contributor Author

cc @targos @rvagg

@maclover7
Copy link
Contributor Author

Once this has been approved, a release has been published to npm, and the new package has been installed on the web server, the following command should be run through the dist user on the web server to regenerate the index.json and index.tab files:

nodejs-dist-indexer --dist "/home/dist/nodejs/release" --indexjson "/home/dist/nodejs/release/index.json"  --indextab "/home/dist/nodejs/release/index.tab"

Copy link
Member

@Trott Trott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rubber-stamp LGTM

dist-indexer.js Outdated
}
})

fetch(uvVersionUrl[3], gitref, function (err, rawData) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you're going to need to nest this inside the previous fetch() otherwise it's going to run in parallel and likely conflict. i.e. indent all of this plus the two lines below it by 2 spaces and move the }) just above here down to the bottom

@maclover7
Copy link
Contributor Author

Sorry about that, fixed the indentation.

@rvagg rvagg merged commit 9ba1f31 into nodejs:master Aug 2, 2018
@rvagg
Copy link
Member

rvagg commented Aug 2, 2018

done and deployed and appears to be working nicely, changes may take a bit of time to show up in /release/ and a bit longer in the other directories, if anyone's impatient for forced updates I can give it a kick

@maclover7 maclover7 deleted the jm-fix-libuv branch August 2, 2018 22:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants