-
Notifications
You must be signed in to change notification settings - Fork 375
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
Node FIXED & Updated (and install.sh corrected) #173
Conversation
…me of node to follow nodejs.org naming convetion of 6.x versions
to use these files yourself (to test or to fix the issues) simply copy the *.rb files to /usr/local/crew/packages/ and you'll be able to do a crew install node_current and you'll have node with NPM installed. (Now a days with that you can almost do ANYTHING!) |
Mono package added. .Net is coming people! |
source_url ({ | ||
i686: "https://www.dropbox.com/s/d1omw087ilkh5oq/jdk1.8.0_25_i686.tar.gz?dl=0", | ||
x86_64: "https://www.dropbox.com/s/ykw2jt797cpghfy/jdk1.8.0_65_x86_64.tar.gz?dl=0" | ||
}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@thedamian I'm always trying not to complain about indentation, but this is so visible 😀
@thedamian what about users who already have node_stable installed? |
If you're still there. It's fixed.
|
Recently formattet my chromebook pixel and wanted to try everyone's change of install.sh so I've merged pull chromebrew#176 into mine to try it.
Reverting back the changes I was trying for pull 178 in the master repo
I'm bad with my reverts because I'm reverting through github since I'm on my virgin chromebook
Just did a powerwash of my chromebook. Went to regular user and back to developer mode (still in stable channel) and then ran MY install.sh with success and installed NODE from my version of the projects. everything is looking good. I tried pull 178 (the removing of the sudo) but it didn't work. nothing got created and nothing was running (hence why I had to do a powerwash) |
Looks like it's fine then. Thanks for all the work! |
Fixes issue: #155 and #143 and #138
Node is Fixed (sorry for the delay, ready below as to why it took so long if interested)
ALSO the install.sh ln of the gcc to cc (to fix some of the errors out there)
-- What too so long --
I went to the dark side (first moved to crew and then full ubuntu on my chromebook pixel)
But I'm back... and I noticed NODE and NODE_STABLE wasn't installing and my install.sh contribution to make some app builds work wasn't in sudo (which was needed)
the node fix came from stealing of the LinuxBrew formula.
(Always thank the giants who's shoulders you stand on while urinating really far)
ALSO changed the name of "NODE_STABLE" to "NODE_CURRENT" to follow the naming convention of node (NODE!: Stop changing how you name everything!)