-
Notifications
You must be signed in to change notification settings - Fork 46
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
Issues with Yeoman installer #58
Comments
Actually the ruby one works... |
I started on a fresh windows VM and typed cinst yeoman |
I started on a fresh (Windows 7) machine and |
Sorry.. Windows 8 that is. |
really...I did it on Win8 and it went smoothly like it should. Are you doing |
It will fail if you piecemeal it due to the powershell session ending and restarting .... |
Yup yup.. even made sure I had Chocolatey latest. |
I would send you a screenshot if I hadn't already closed down my shell. |
Can you do that again? I pushed up the nodejs fix. |
Best if you can somehow make that fresh again. Otherwise go uninstall ruby/node manually and others if you want. And verify the path (system and user) no longer contains those paths. Then open a fresh command line and hook it up. |
Fixed both optipng and phantomjs to actually end up on the path. They are in the binDir - if you set the environment variable, you can tell them to go anywhere. The lack of the env var makes it go to systemdrive |
Sweet -- sorry about that. These types of things are so difficult to test without actually baking the pkg, releasing, and then trying it out. I've put together a handful of Nuget packages that mess with DTE in Visual Studio -- always such a PITA. |
I cleaned up everything, then reran and you are correct re: I think I must have manually installed Ruby first via |
Interesting.. when the install finished up, it never ran
PS C:\Chocolatey\chocolateyInstall> type install.log
Attempting to resolve dependency 'Compass (ò 0.12.2)'.
Attempting to resolve dependency 'ruby (ò 1.8.7)'.
Attempting to resolve dependency 'git'.
Attempting to resolve dependency 'git.install (= 1.7.11)'.
Attempting to resolve dependency 'nodejs.install (ò 0.8.1)'.
Attempting to resolve dependency 'libjpeg-turbo (ò 1.2.1)'.
Attempting to resolve dependency 'OptiPNG (ò 0.7.1)'.
Attempting to resolve dependency 'PhantomJS (ò 1.6.1)'.
Successfully installed 'ruby 1.8.7.35800'.
Successfully installed 'Compass 0.12.2'.
Successfully installed 'git.install 1.7.11'.
Successfully installed 'git 1.7.11'.
Successfully installed 'nodejs.install 0.8.9.20120913'.
Successfully installed 'libjpeg-turbo 1.2.1'.
Successfully installed 'OptiPNG 0.7.1.20120913'.
Successfully installed 'PhantomJS 1.6.1.20120913'. |
Well it didn't install yeoman for some reason. Was the folder already there? |
I went through and trashed everything first..
It's possible that I missed removing yeoman from chocolatey\lib ... but if that were the case, I would have need to run |
Unknown. Put it in a folder. Use straight nuget and then erase all deps. Then run it again. If it just adds the dependencies, that's what you had going. |
Thinking this was good to close? |
Yeah, I think it's good to close.. I must have done something wrong.. if no one else is reporting issues on the Yeoman thread, worth closing. |
Ok... so here are the issues, based on a clean machine.
gem
and install Compass -- the installer blows up (b/cgem
isn't in PATH).npm
it blows up (b/cnpm
isn't in PATH).For the first two, the bug is in Chocolatey -- it doesn't recapture the modified PATH (or any other env variables for that matter after running an installer). IMHO, its Chocolatey's obligation to do this.
I think you're aware of this issue.. but I didn't see you handling this anywhere in the code after a quick scan. I provide a fix in PowerShell to recapture the path.
chocolatey-archive/chocolatey#140 (comment)
The text was updated successfully, but these errors were encountered: