For my future self.
Due to an issue with choco-cleaner versions [WayBack] 0.0.6 and [WayBack] 0.0.7, I needed to ensure it was installed as version [WayBack] 0.0.5.2 and keep it that version.
Not sure if this is the canonical way, but this worked:
choco uninstall --yes choco-cleaner choco install --yes choco-cleaner --version 0.0.5.2 choco pin add --name=choco-cleaner --version 0.0.5.2 choco pin list
This worked to revert:
choco pin remove --name=choco-cleaner choco pin list choco upgrade --yes choco-cleaner
Aftere this upgrade, choco-cleaner version 0.0.7.1 shows a nice error message when the environment variable %ChocolateyToolsLocation% fails to exist.
In that case calling RefreshEnv.cmd will create that environment variable.
Related:
- [WayBack] Chocolatey Software | Commandsinstall: Examples
- [WayBack] Chocolatey Software | Commandspin: examples
- [WayBack] Chocolatey Software | (unofficial) Choco Cleaner (Script + Task) 0.0.7: releasenotes
- [WayBack] Lack of `ChocolateyToolsLocation` environment variable causes `choco-cleaner` to fail in an UAC console · Issue #143 · bcurran3/ChocolateyPackages · GitHub
Default
%ChocolateyToolsLocation%location is%systemdrive%\toolsaccording to [WayBack] https://github.com/chocolatey/choco/blob/master/src/chocolatey.resources/helpers/functions/Get-ToolsLocation.ps1#L61 - [WayBack] Installed to c:\tools\bcurran3 · Issue #112 · bcurran3/ChocolateyPackages · GitHub
The readme.md on GitHub is out of sync… a bunch of stuff is that I need to get to eventually.
The new package page on chocolatey.org should be current and has this:
Release Notes
INSTRUCTIONS:
Edit C:\tools\BCURRAN3\choco-package-list-backup.config to customize your backup(s). It’s easy, there are comments.
From PowerShell or the Command Prompt, type CHOCO-PACKAGE-LIST-BACKUP to backup your Chocolatey packages list.
From Windows, click Chocolatey Package List Backup in the Windows Start Menu or Package List Backup inside the Chocolatey folder if Chocolatey Shortcuts is installed.
CHANGELOG:
2019.08.27 – can now put title and summary info into the packages.config file, new -EditConfig parameter to edit the config file, Now works from Command Prompt as well as PowerShell, script installation endpoint changed, config file renamed from .xml to .config
–jeroen





