Skip to content
This repository was archived by the owner on Dec 15, 2022. It is now read-only.

Revert changes from #43 #45

Closed
wants to merge 1 commit into from
Closed

Conversation

Arcanemagus
Copy link
Contributor

Reverts the changes from #43 per #43 (comment).

Reverts the changes from atom#43 per atom#43 (comment).
@Arcanemagus
Copy link
Contributor Author

@joefitzgerald, @thomasjo Any reason this hasn't been merged yet? The changes in #43 were supposedly causing issues with packages, and have not yet been reverted...

@joefitzgerald
Copy link
Contributor

@thomasjo you merged #43, what do you think?

@thomasjo
Copy link
Contributor

thomasjo commented Aug 2, 2016

I don't recall anyone saying this caused any issues. I'm not against reverting it, but now we're at least consistent across platforms. My point was always that we should be consistent.

The CI scripts are a royal mess and desperately needs to be refactored... it's on my list, but likely won't happen until September. I'm leaning towards leaving things as they are now unless someone can point me to actual evidence that what we have now is causing problems. I'm not looking for theoretical problems, only real and current problems.

@Arcanemagus
Copy link
Contributor Author

Okay, closing this then 😉.

@Arcanemagus Arcanemagus closed this Aug 2, 2016
@Arcanemagus Arcanemagus deleted the revert-43 branch August 2, 2016 19:05
@Arcanemagus
Copy link
Contributor Author

As a note, #49 essentially did this reversion if the flag to use the bundled node is enabled (which it is by default).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants