Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

introduce NODEJS_ORG_MIRROR and IOJS_ORG_MIRROR #878

Closed
wants to merge 1 commit into from

Conversation

rvagg
Copy link
Member

@rvagg rvagg commented Feb 12, 2016

/R= @nodejs/build @ljharb

to be followed soon by a semver-major that removes the NVM_ variants as these cause grief, see #787

@ljharb
Copy link
Member

ljharb commented Feb 12, 2016

👍

@mgol
Copy link

mgol commented Feb 12, 2016

I can't judge the build & tests but source changes look good. 👍

@ralphtheninja
Copy link
Contributor

LGTM

@rvagg
Copy link
Member Author

rvagg commented Feb 13, 2016

Should we do a warn message (npmlog style) whenever NVM_* is encountered? I can't recall the details of how this is used internally in nvm but would it hit many users not trying to use those variables to control node-gyp? @ljharb?

This was referenced Feb 13, 2016
@ralphtheninja
Copy link
Contributor

Should we do a warn message (npmlog style) whenever NVM_* is encountered?

Like a deprecated warning? +1

@ljharb
Copy link
Member

ljharb commented Feb 13, 2016

@rvagg it's primarily that it's an env var that while I don't intend to change, I might - a warning seems reasonable so people know to switch.

@rvagg rvagg force-pushed the nodejs_org_mirror branch from 6a87f83 to 3350bf9 Compare February 15, 2016 01:17
@rvagg
Copy link
Member Author

rvagg commented Feb 15, 2016

Added a warning, run the tests to see it output:

gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR

@bnoordhuis can I ask for a review here as well please?

@zkat @iarna are there any guidelines on outputting warnings with npmlog? Is this wording going to be OK when it starts showing up for users who have that env var set?


var release = processRelease([], { opts: {} }, 'v3.2.24', {
name: 'io.js',
headersUrl: 'http://foo.bar/v3.2.24/iojs-v3.2.24-headers.tar.gz'
Copy link
Member

Choose a reason for hiding this comment

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

You use 'https://nodejs.org/` in the first two tests but http://foo.bar here and in the next test. Is that intentional?

Copy link
Member Author

Choose a reason for hiding this comment

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

No, search/replace error, the test should find that process.release is mostly ignored and it's not testing that as it is now. Thanks for noticing, will fix!

@bnoordhuis
Copy link
Member

JS changes LGTM with a question, no opinion on the docker shell script. There are some long lines but that's not really a thing with node-gyp.

Deprecate NVM_NODEJS_ORG_MIRROR and NVM_IOJS_ORG_MIRROR as they
were only ever intended to be internal nvm environment variables.
These will be removed in the next semver-major release.
@rvagg rvagg force-pushed the nodejs_org_mirror branch from 3350bf9 to 95ed796 Compare February 15, 2016 09:14
rvagg added a commit that referenced this pull request Feb 16, 2016
Deprecate NVM_NODEJS_ORG_MIRROR and NVM_IOJS_ORG_MIRROR as they
were only ever intended to be internal nvm environment variables.
These will be removed in the next semver-major release.

PR-URL: #878
Reviewed-By: ralphtheninja
Reviewed-By: Ben Noordhuis <[email protected]>
@rvagg rvagg closed this Feb 16, 2016
@rvagg rvagg deleted the nodejs_org_mirror branch February 16, 2016 04:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants