interesting
/
libui
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Hm, Chocolatey is being annoying...

This commit is contained in:
Pietro Gagliardi 2019-04-07 01:11:18 -04:00
parent 651d502624
commit 21591e4f6f
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
azure-pipelines/windows-setup-mingw.yml
View File

@ -5,6 +5,9 @@ parameters:
steps: steps:
- powershell: | - powershell: |
WriteError "$env:ChocolateyInstall"
dir "$env:ChocolateyInstall" | Write-Error
dir "$env:ChocolateyInstall\lib" | Write-Error
$chocopath = where.exe choco.exe | Get-Item $chocopath = where.exe choco.exe | Get-Item
# apparently they didn't think to add this functionality from the start (multiple joins was only added in PowerShell 6 and Azure Pipelines is using 5.x), and the direct-CLR approach actually behaves differently (and I would need to check which version of .net Azure Pipelines is using anyway, since our use case isn't one of those cases where it behaves differently) # apparently they didn't think to add this functionality from the start (multiple joins was only added in PowerShell 6 and Azure Pipelines is using 5.x), and the direct-CLR approach actually behaves differently (and I would need to check which version of .net Azure Pipelines is using anyway, since our use case isn't one of those cases where it behaves differently)
$chocopath = Join-Path -Path $chocopath.Directory -ChildPath "install" | Join-Path -ChildPath "${{ parameters.which }}" | Join-Path -ChildPath "bin" $chocopath = Join-Path -Path $chocopath.Directory -ChildPath "install" | Join-Path -ChildPath "${{ parameters.which }}" | Join-Path -ChildPath "bin"