## Where communities thrive

• Join over 1.5M+ people
• Join over 100K+ communities
• Free without limits
##### Activity
Rob Reynolds
@ferventcoder
The only issue is in how you include the files - nuget gets confused if the files to include is a backslash. We need to fix that in nuget.core
Bricktop
@MarcelMue
@ferventcoder True, there were several decisions that lead to a gradle plugin for now ( development team being familiar gradle already, the use of different OS in the build infrastructure and some concerns about adding mono to every buildslave), that said I think a switch to mono later on could very well happen
Jesse Connor
@jesseconnr
When handling log files for msi installs are you guys having to create the log folder for the .msi install to succeed? Seems the .msi just errors out if I don't, but looking through other packages for examples I haven't seen anyone manually creating the path for the log file.
This message was deleted
Rob Reynolds
@ferventcoder
@jesseconnr the MSI Log filter needs ”” and not ’'
it’s super finicky
RichardJFoster
@RichardJFoster
Evenin' all. This is a curiosity thing. I notice that VirtualBox, which looks like it should be a trusted automatic package, has not been updated to include the recent 5.0.16 release. Not having a clue what I'm doing I looked at the virtualbox.ketarin.xml file, and verified that everything seems kosher. What might be preventing the detection and subsequent chocolatey coating of the new release (which occurred on the 4th according to the website)?
Rob Reynolds
@ferventcoder
I will take a look, likely tomorrow early to see what is going on with the box running that
RichardJFoster
@RichardJFoster
Sounds good. Thank you.
Jesse Connor
@jesseconnr
@ferventcoder wouldn't using back-ticks be the right way to escape the quotes in the chocolateyInstall.ps1 file?
[string] $pkgArgs = "/qn /norestart /l*v "$($logPath)\$($pkgName).log" " or are you saying I should double quote even after that? ""$($logPath)\$($pkgName).log"" Jesse Connor @jesseconnr Either way, creating the directory solves the issue. I've got another problem now where if I install from a package file that doesn't have the version in the name and the package is already installed, it fails with an error about the package not being found in the source. Ex. choco install -fy package.nupkg, if package is already installed it fails unless it's presented as package.1.0.0.nupkg. Rob Reynolds @ferventcoder @jesseconnr I believe that is fixed. It may only be in the 0.9.10 beta though If it is not fixed, the issue is logged The workaround is to call install name -s folder\of\nupkg Also make sure that it doesn't have .\ on the front of it - it doesn't like that And ya, the folder must exist for msi logging Backticks is great, that is what I was saying. Double double quotes will just make it error Crack Duck @n1trux hey, I asked a few people what they think about Choco and found out that there are three major concerns which really put them off: 1) the complicated install command, 2) not trusting choco devs and 3) not having its own repository but rather pulling from untrusted servers. Here's the thread for anyone who's interested: https://www.reddit.com/r/sysadmin/comments/4apjvs aronovgj @aronovgj It is a copy and paste command, choco is open source and these "untrusted servers" are official servers of the software developers. Didn't read the reddit... Also for businesses you wouldn't use chocolatey.org but build your own repo Rob Reynolds @ferventcoder @n1trux ^^ All of these concerns feel like a bit of folks being misinformed. I'll address the thread later Brandon H @bc3tech sounds very familiar to what i faced at a previous (very paranoid) enterprise when i pitched (and later set up) chocolatey. 9 times outta 10 it is exactly what you're looking for. so you gotta either change your mind (don't need a central software repo) or change your policy (choco is good) a room full of managers' jaws dropped when i showed them chocolatey the first time and there were IT personnel in there. they all agreed it was the way to go. Rob Reynolds @ferventcoder Just keep in mind most organizations never touch the community repo bc3tech++ The chocolatiest bot this side of the Mississippi @choco-bot bc3tech gained a level! (Karma: 3) Rob Reynolds @ferventcoder For relaying those concerns to me to address Jesse Connor @jesseconnr An easy way to alleviate some of that concern and add functionality would be for packages to allow specifying the source of the installer instead of embedding the url. Though you could end up with some version issues I suppose. aronovgj @aronovgj regarding ccenhancer package that failed: http://pastebin.com/93Kw0hLk still don't get it Jesse Connor @jesseconnr @aronovgj looks like one of your objects in the Join-Path is an object and not a string aronovgj @aronovgj yes i see that. why does this happen? Jesse Connor @jesseconnr probably this,$folder = Get-ChildItem $unzipLocation | Where-Object {$_.Name -match "CCEnhancer*"}
aronovgj
@aronovgj
yes, any idea how to get it right? because it works on my machine and in the verifier
Jesse Connor
@jesseconnr
I've got to jump on a conference call for a bit, but if you don't have it when I get back I'll take a look
wherever it didn't work, maybe it's a powershell version issue
aronovgj
@aronovgj
thanks. i looked it up and it should work with posh2 as far as i got it
also it works in my test environment which has posh2
Gary Ewan Park
@gep13
@aronovgj also, might be worth getting them to update to latest chocolatey as well
@aronovgj where did you get the paste bin contents from? Can you get details from the person about what OS, etc, they are on?
I think that sort of information is included by default in the latest chocolatey debug logs
aronovgj
@aronovgj
it is 0.9.9.8
choco version
it is in the log
actualy it is all in the log