These are chat archives for chocolatey/chocolatey-oneget

2nd
Mar 2015
Joel Bennett
@Jaykul
Mar 02 2015 07:07
Wow, four separate CI builds?
Gary Ewan Park
@gep13
Mar 02 2015 07:24
@Jaykul well, technically, 3, but yes :-)
the fourth is a check to ensure that the contributor has signed the CLA, it doesn't do anything else
we have Travis, TeamCity and AppVeyor
TeamCity and AppVeyor, while they are doing the same thing just now, we have plans on increasing the amount of work that is done on the AppVeyor build
since AppVeyor provisions a new VM for each build, we can do "stuff" in that build that we can't do on the TeamCity build, so we can start to test out scenarios to ensure they are working on each new release
Jaykul @Jaykul nods
Joel Bennett
@Jaykul
Mar 02 2015 07:28
travis is failing
Gary Ewan Park
@gep13
Mar 02 2015 07:28
ha ha, great minds!
I just kicked the build, as it looked like the restoring of nuget packages timed out
Joel Bennett
@Jaykul
Mar 02 2015 07:29
I saw that
Gary Ewan Park
@gep13
Mar 02 2015 07:29
I am assuming a glitch in the matrix
hopefully a second attempt will work
Joel Bennett
@Jaykul
Mar 02 2015 07:29
The other one passed, so there :-p
Gary Ewan Park
@gep13
Mar 02 2015 07:29
ha ha :-)
Gary Ewan Park
@gep13
Mar 02 2015 07:38
hmm, the Travis build failed again :-(
not sure what is going on there
will wait and see what @ferventcoder has to say about it
before doing any more prodding
Joel Bennett
@Jaykul
Mar 02 2015 08:12
Yeah, no biggie -- I'm done for the night anyway
Need to get @ferventcoder's approval for the general approach before I do the same thing with the list (package search) command ;-)
Rob Reynolds
@ferventcoder
Mar 02 2015 13:50
travis-ci has been failing on restoring nuget builds. Could be a flaky nuget connection
Joel Bennett
@Jaykul
Mar 02 2015 20:57
yeah, I assumed it wasn't my fault ;-)
Eirik Brandtzæg
@eirikb
Mar 02 2015 22:09
I tried Install-Package nodejs.install (Windows 10). This works, although npm or node does not seem to be added to path, all I get is "... is not recognized as an internal or external command...". If I try with Chocolatey directly (cinst nodejs.install) it works, although I have to log out/in. Any clues to what I can do?
Joel Bennett
@Jaykul
Mar 02 2015 22:29
I don't think the current provider runs install scripts
but I'm not sure
Basically, the only answer I have is: wait for the new Chocolatey provider
or use choco.exe
Eirik Brandtzæg
@eirikb
Mar 02 2015 22:32
Looks like you are right. The installed packages are simply not installed
Downloaded and unpacked into the Chocolatey-folder, but that seems to be it
Joel Bennett
@Jaykul
Mar 02 2015 22:39
Yeah. this channel is about ... fixing that
;)
But the fix isn't ready
Eirik Brandtzæg
@eirikb
Mar 02 2015 22:40
Well Windows 10 isn't even released, so to be honest I would be a bit surprised if it "just worked" :) I didn't even know about OneGet before today!
Joel Bennett
@Jaykul
Mar 02 2015 22:42
The goal is for this part, at least, to work by ignite conference ;-)
Eirik Brandtzæg
@eirikb
Mar 02 2015 22:42
I've been trying to convince my coworkers to embrace Chocolatey for years now, and with a native client that becomes much easier
Wonder why cinst won't update path on windows 10 though, that is a bit strange. If I use PS and call $env:Path = [System.Environment]:GetEnvironmentVariable("Path", "Machine") it is updated correctly
Joel Bennett
@Jaykul
Mar 02 2015 22:47
oh
Sounds like it's setting the environment variable in machine scope ...
but NOT in process scope.
Eirik Brandtzæg
@eirikb
Mar 02 2015 22:47
I only tried with "Machine". I could try with others if you like, just to test. I only know about "Machine" and "User"
Joel Bennett
@Jaykul
Mar 02 2015 22:48
It would have to do both to make sure it worked without closing your console and opening a new one.
you in POwerShell?
Eirik Brandtzæg
@eirikb
Mar 02 2015 22:48
Tried both PowerShell and cmd. Closing does not help, have to log in/out, or call the command snippet I mentioned
Joel Bennett
@Jaykul
Mar 02 2015 22:48
wait, let me rephrase that
If it's setting the machine path
It SHOULD get read when you create a new app from the OS shell
So if you have, for instance, ConEmu
a new tab won't work
you'd have to exit ConEmu and restart it
But ... THAT should work
What would be better is if the installer actually set the machine level AND process level
Eirik Brandtzæg
@eirikb
Mar 02 2015 22:50
But why does it work in Windows 8.1, but not in 10?
Joel Bennett
@Jaykul
Mar 02 2015 22:51
Maybe they changed (read that "broke") how the environment updates.
Eirik Brandtzæg
@eirikb
Mar 02 2015 22:52
Sounds plausible
Well no big deal for me, I was mostly curious, and excited about OneGet. Thanks for feedback, now I'm going to bed. Bye :)
Rob Reynolds
@ferventcoder
Mar 02 2015 23:03
@eirikb I think it does update the path, it’s a Windows issue with shells
:)
but I don’t have a windows 10 box with the updated preview yet