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

docs: reorder steps for first timers #15898

Closed
wants to merge 2 commits into from
Closed

Conversation

joeldart
Copy link
Contributor

@joeldart joeldart commented Oct 6, 2017

found at node interactive code and learn.
when you have never built, running macosx-firewall.sh gives errors as
/out does not exist. reordering this after the build step in the doc
will remove that error.

Checklist
Affected core subsystem(s)

doc

found at node interactive code and learn.
when you have never built, running macosx-firewall.sh gives errors as
/out does not exist. reordering this after the build step in the doc
will remove that error
@nodejs-github-bot nodejs-github-bot added build Issues and PRs related to build files or the CI. doc Issues and PRs related to the documentations. labels Oct 6, 2017
@Trott Trott added the code-and-learn Issues related to the Code-and-Learn events and PRs submitted during the events. label Oct 6, 2017
BUILDING.md Outdated
* On macOS you may want to setup [firewall rules](tools/macosx-firewall.sh)
to avoid popups asking to accept incoming network connections when running tests:

If the path to your build directory contains a space, the build will likely fail.
Copy link
Member

Choose a reason for hiding this comment

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

Hi, @joeldart! Welcome and thanks for this! This line about spaces in the directory should remain where it was above. Moving the other ones seems good to me. Can you move this line back?

@gibfahn
Copy link
Member

gibfahn commented Oct 9, 2017

This has conflicts as e8bf4d5 landed, which aims to solve the same problem.

@Trott
Copy link
Member

Trott commented Oct 10, 2017

Ah, looks like this is fixed then? I'm going to close this one, but feel free to comment (or re-open if GitHub lets you) if you think it should remain open.

Happy to see @joeldart has #15848 open too so they'll still get a commit into Node.js if all goes well there (which it appears that it will--would have landed that one right now except that it needs a CI run first).

@Trott Trott closed this Oct 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Issues and PRs related to build files or the CI. code-and-learn Issues related to the Code-and-Learn events and PRs submitted during the events. doc Issues and PRs related to the documentations.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants