diff --git a/automatic/cyberghost-vpn/ReadMe.md b/automatic/cyberghost-vpn/ReadMe.md new file mode 100644 index 000000000..9349609d8 --- /dev/null +++ b/automatic/cyberghost-vpn/ReadMe.md @@ -0,0 +1,19 @@ +[![](https://img.shields.io/chocolatey/v/cyberghost-vpn?color=green&label=cyberghost-vpn)](https://chocolatey.org/packages/cyberghost-vpn) [![](https://img.shields.io/chocolatey/dt/cyberghost-vpn)](https://chocolatey.org/packages/cyberghost-vpn) + +## PKGTITLE + +--- + +PKGDesc + +--- + +#### [choco://cyberghost-vpn](choco://cyberghost-vpn) +To use choco:// protocol URLs, install [(unofficial) choco:// Protocol support ](https://chocolatey.org/packages/choco-protocol-support) + +### Package-specific issue +If this package isn't up-to-date for some days, [Create an issue](https://github.com/tunisiano187/Chocolatey-packages/issues/new/choose) + +Support the package maintainer and [![Patreon](https://cdn.jsdelivr.net/gh/tunisiano187/Chocolatey-packages@d15c4e19c709e7148588d4523ffc6dd3cd3c7e5e/icons/patreon.png)](https://www.patreon.com/tunisiano) + +--- diff --git a/automatic/cyberghost-vpn/_TODO.txt b/automatic/cyberghost-vpn/_TODO.txt new file mode 100644 index 000000000..50bca03a7 --- /dev/null +++ b/automatic/cyberghost-vpn/_TODO.txt @@ -0,0 +1,131 @@ +TODO + +1. Determine Package Use: + + Organization? Internal Use? - You are not subject to distribution + rights when you keep everything internal. Put the binaries directly + into the tools directory (as long as total nupkg size is under 1GB). + When bigger, look to use from a share or download binaries from an + internal location. Embedded binaries makes for the most reliable use + of Chocolatey. Use `$fileLocation` (`$file`/`$file64`) and + `Install-ChocolateyInstallPackage`/`Get-ChocolateyUnzip` in + tools\chocolateyInstall.ps1. + + You can also choose to download from internal urls, see the next + section, but ignore whether you have distribution rights or not, it + doesn't apply. Under no circumstances should download from the + internet, it is completely unreliable. See + https://docs.chocolatey.org/en-us/community-repository/community-packages-disclaimer + to understand the limitations of a publicly available repository. + + Community Repository? + Have Distribution Rights? + If you are the software vendor OR the software EXPLICITLY allows + redistribution and the total nupkg size will be under 200MB, you + have the option to embed the binaries directly into the package to + provide the most reliable install experience. Put the binaries + directly into the tools folder, use `$fileLocation` (`$file`/ + `$file64`) and `Install-ChocolateyInstallPackage`/ + `Get-ChocolateyUnzip` in tools\chocolateyInstall.ps1. Additionally, + fill out the LICENSE and VERIFICATION file (see 3 below and those + files for specifics). + + NOTE: You can choose to download binaries at runtime, but be sure + the download location will remain stable. See the next section. + + Do Not Have Distribution Rights? + - Note: Packages built this way cannot be 100% reliable, but it's a + constraint of publicly available packages and there is little + that can be done to change that. See + https://docs.chocolatey.org/en-us/community-repository/community-packages-disclaimer + to better understand the limitations of a publicly available + repository. + Download Location is Publicly Available? + You will need to download the runtime files from their official + location at runtime. Use `$url`/`$url64` and + `Install-ChocolateyPackage`/`Install-ChocolateyZipPackage` in + tools\chocolateyInstall.ps1. + Download Location is Not Publicly Available? + Stop here, you can't push this to the community repository. You + can ask the vendor for permission to embed, then include a PDF of + that signed permission directly in the package. Otherwise you + will need to seek alternate locations to non-publicly host the + package. + Download Location Is Same For All Versions? + You still need to point to those urls, but you may wish to set up + something like Automatic Updater (AU) so that when a new version + of the software becomes available, the new package version + automatically gets pushed up to the community repository. See + https://docs.chocolatey.org/en-us/create/automatic-packages#automatic-updater-au + +2. Determine Package Type: + +- Installer Package - contains an installer (everything in template is + geared towards this type of package) +- Zip Package - downloads or embeds and unpacks archives, may unpack + and run an installer using `Install-ChocolateyInstallPackage` as a + secondary step. +- Portable Package - Contains runtime binaries (or unpacks them as a + zip package) - cannot require administrative permissions to install + or use +- Config Package - sets config like files, registry keys, etc +- Extension Package - Packages that add PowerShell functions to + Chocolatey - https://docs.chocolatey.org/en-us/features/extensions +- Template Package - Packages that add templates like this for `choco + new -t=name` - https://docs.chocolatey.org/en-us/guides/create/create-custom-package-templates +- Other - there are other types of packages as well, these are the main + package types seen in the wild + +3. Fill out the package contents: + +- tools\chocolateyBeforeModify.ps1 - remove if you have no processes + or services to shut down before upgrade/uninstall +- tools\LICENSE.txt / tools\VERIFICATION.txt - Remove if you are not + embedding binaries. Keep and fill out if you are embedding binaries + in the package AND pushing to the community repository, even if you + are the author of software. The file becomes easier to fill out + (does not require changes each version) if you are the software + vendor. If you are building packages for internal use (organization, + etc), you don't need these files as you are not subject to + distribution rights internally. +- tools\chocolateyUninstall.ps1 - remove if autouninstaller can + automatically uninstall and you have nothing additional to do during + uninstall +- Readme.txt - delete this file once you have read over and used + anything you've needed from here +- nuspec - fill this out, then clean out all the comments (you may wish + to leave the headers for the package vs software metadata) +- tools\chocolateyInstall.ps1 - instructions in next section. + +4. ChocolateyInstall.ps1: + +- For embedded binaries - use `$fileLocation` (`$file`/`$file64`) and + `Install-ChocolateyInstallPackage`/ `Get-ChocolateyUnzip`. +- Downloading binaries at runtime - use `$url`/`$url64` and + `Install-ChocolateyPackage` / `Install-ChocolateyZipPackage`. +- Other needs (creating files, setting registry keys), use regular + PowerShell to do so or see if there is a function already defined: + https://docs.chocolatey.org/en-us/create/functions +- There may also be functions available in extension packages, see + https://community.chocolatey.org/packages?q=id%3A.extension for examples and + availability. +- Clean out the comments and sections you are not using. + +5. Test the package to ensure install/uninstall work appropriately. + There is a test environment you can use for this - + https://github.com/chocolatey/chocolatey-test-environment + +6. Learn more about Chocolatey packaging - go through the workshop at + https://github.com/chocolatey/chocolatey-workshop + You will learn about + - General packaging + - Customizing package behavior at runtime (package parameters) + - Extension packages + - Custom packaging templates + - Setting up an internal Chocolatey.Server repository + - Adding and using internal repositories + - Reporting + - Advanced packaging techniques when installers are not friendly to + automation + +7. Delete this file. diff --git a/automatic/cyberghost-vpn/cyberghost-vpn.nuspec b/automatic/cyberghost-vpn/cyberghost-vpn.nuspec new file mode 100644 index 000000000..6c4f22dd1 --- /dev/null +++ b/automatic/cyberghost-vpn/cyberghost-vpn.nuspec @@ -0,0 +1,83 @@ + + + + + + + + + + + + + + + + + + + cyberghost-vpn + + + + 0.0 + + + + + + + + cyberghost-vpn (Install) + __REPLACE_AUTHORS_OF_SOFTWARE_COMMA_SEPARATED__ + + https://_Software_Location_REMOVE_OR_FILL_OUT_ + + + + + + + + + + + cyberghost-vpn SPACE_SEPARATED + __REPLACE__ + __REPLACE__MarkDown_Okay + + +**Please Note**: This is an automatically updated package. If you find it is +out of date by more than a day or two, please contact the maintainer(s) and +let them know the package is no longer updating correctly. + + + + + + + + + + + + + + + + + diff --git a/automatic/cyberghost-vpn/tools/LICENSE.txt b/automatic/cyberghost-vpn/tools/LICENSE.txt new file mode 100644 index 000000000..3b1a53fbd --- /dev/null +++ b/automatic/cyberghost-vpn/tools/LICENSE.txt @@ -0,0 +1,11 @@ + +Note: Include this file if including binaries you have the right to distribute. +Otherwise delete. this file. + +===DELETE ABOVE THIS LINE AND THIS LINE=== + +From: + +LICENSE + + diff --git a/automatic/cyberghost-vpn/tools/VERIFICATION.txt b/automatic/cyberghost-vpn/tools/VERIFICATION.txt new file mode 100644 index 000000000..5b1394212 --- /dev/null +++ b/automatic/cyberghost-vpn/tools/VERIFICATION.txt @@ -0,0 +1,13 @@ + +Note: Include this file if including binaries you have the right to distribute. +Otherwise delete. this file. If you are the software author, you can mention +this. + +===DELETE ABOVE THIS LINE AND THIS LINE=== + +VERIFICATION +Verification is intended to assist the Chocolatey moderators and community +in verifying that this package's contents are trustworthy. + + + \ No newline at end of file diff --git a/automatic/cyberghost-vpn/tools/chocolateybeforemodify.ps1 b/automatic/cyberghost-vpn/tools/chocolateybeforemodify.ps1 new file mode 100644 index 000000000..eadc55ffd --- /dev/null +++ b/automatic/cyberghost-vpn/tools/chocolateybeforemodify.ps1 @@ -0,0 +1,9 @@ +# This runs before upgrade or uninstall. +# Use this file to do things like stop services prior to upgrade or uninstall. +# NOTE: It is an anti-pattern to call chocolateyUninstall.ps1 from here. If you +# need to uninstall an MSI prior to upgrade, put the functionality in this +# file without calling the uninstall script. Make it idempotent in the +# uninstall script so that it doesn't fail when it is already uninstalled. +# NOTE: For upgrades - like the uninstall script, this script always runs from +# the currently installed version, not from the new upgraded package version. + diff --git a/automatic/cyberghost-vpn/tools/chocolateyinstall.ps1 b/automatic/cyberghost-vpn/tools/chocolateyinstall.ps1 new file mode 100644 index 000000000..ec5589689 --- /dev/null +++ b/automatic/cyberghost-vpn/tools/chocolateyinstall.ps1 @@ -0,0 +1,151 @@ +# IMPORTANT: Before releasing this package, copy/paste the next 2 lines into PowerShell to remove all comments from this file: +# $f='c:\path\to\thisFile.ps1' +# gc $f | ? {$_ -notmatch "^\s*#"} | % {$_ -replace '(^.*?)\s*?[^``]#.*','$1'} | Out-File $f+".~" -en utf8; mv -fo $f+".~" $f + +# 1. See the _TODO.md that is generated top level and read through that +# 2. Follow the documentation below to learn how to create a package for the package type you are creating. +# 3. In Chocolatey scripts, ALWAYS use absolute paths - $toolsDir gets you to the package's tools directory. +$ErrorActionPreference = 'Stop' # stop on all errors +#Items that could be replaced based on what you call chocopkgup.exe with +#{{PackageName}} - Package Name (should be same as nuspec file and folder) |/p +#{{PackageVersion}} - The updated version | /v +#{{DownloadUrl}} - The url for the native file | /u +#{{PackageFilePath}} - Downloaded file if including it in package | /pp +#{{PackageGuid}} - This will be used later | /pg +#{{DownloadUrlx64}} - The 64-bit url for the native file | /u64 +#{{Checksum}} - The checksum for the url | /c +#{{Checksumx64}} - The checksum for the 64-bit url | /c64 +#{{ChecksumType}} - The checksum type for the url | /ct +#{{ChecksumTypex64}} - The checksum type for the 64-bit url | /ct64 + +$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)" +# Internal packages (organizations) or software that has redistribution rights (community repo) +# - Use `Install-ChocolateyInstallPackage` instead of `Install-ChocolateyPackage` +# and put the binaries directly into the tools folder (we call it embedding) +#$fileLocation = Join-Path $toolsDir 'NAME_OF_EMBEDDED_INSTALLER_FILE' +# If embedding binaries increase total nupkg size to over 1GB, use share location or download from urls +#$fileLocation = '\\SHARE_LOCATION\to\INSTALLER_FILE' +# Community Repo: Use official urls for non-redist binaries or redist where total package size is over 200MB +# Internal/Organization: Download from internal location (internet sources are unreliable) +$url = '{{DownloadUrl}}' # download url, HTTPS preferred +$url64 = '{{DownloadUrlx64}}' # 64bit URL here (HTTPS preferred) or remove - if installer contains both (very rare), use $url + +$packageArgs = @{ + packageName = $env:ChocolateyPackageName + unzipLocation = $toolsDir + fileType = 'EXE_MSI_OR_MSU' #only one of these: exe, msi, msu + url = $url + url64bit = $url64 + #file = $fileLocation + + softwareName = 'cyberghost-vpn*' #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique + + # Checksums are required for packages which will be hosted on the Chocolatey Community Repository. + # To determine checksums, you can get that from the original site if provided. + # You can also use checksum.exe (choco install checksum) and use it + # e.g. checksum -t sha256 -f path\to\file + checksum = '{{Checksum}}' + checksumType = '{{ChecksumType}}' #default is md5, can also be sha1, sha256 or sha512 + checksum64 = '{{Checksumx64}}' + checksumType64= '{{ChecksumTypex64}}' #default is checksumType + + # MSI + silentArgs = "/qn /norestart /l*v `"$($env:TEMP)\$($packageName).$($env:chocolateyPackageVersion).MsiInstall.log`"" # ALLUSERS=1 DISABLEDESKTOPSHORTCUT=1 ADDDESKTOPICON=0 ADDSTARTMENU=0 + validExitCodes= @(0, 3010, 1641) + # OTHERS + # Uncomment matching EXE type (sorted by most to least common) + #silentArgs = '/S' # NSIS + #silentArgs = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-' # Inno Setup + #silentArgs = '/s' # InstallShield + #silentArgs = '/s /v"/qn"' # InstallShield with MSI + #silentArgs = '/s' # Wise InstallMaster + #silentArgs = '-s' # Squirrel + #silentArgs = '-q' # Install4j + #silentArgs = '-s' # Ghost + # Note that some installers, in addition to the silentArgs above, may also need assistance of AHK to achieve silence. + #silentArgs = '' # none; make silent with input macro script like AutoHotKey (AHK) + # https://community.chocolatey.org/packages/autohotkey.portable + #validExitCodes= @(0) #please insert other valid exit codes here +} + +Install-ChocolateyPackage @packageArgs # https://docs.chocolatey.org/en-us/create/functions/install-chocolateypackage +#Install-ChocolateyZipPackage @packageArgs # https://docs.chocolatey.org/en-us/create/functions/install-chocolateyzippackage +## If you are making your own internal packages (organizations), you can embed the installer or +## put on internal file share and use the following instead (you'll need to add $file to the above) +#Install-ChocolateyInstallPackage @packageArgs # https://docs.chocolatey.org/en-us/create/functions/install-chocolateyinstallpackage + +## Main helper functions - these have error handling tucked into them already +## see https://docs.chocolatey.org/en-us/create/functions + +## Install an application, will assert administrative rights +## - https://docs.chocolatey.org/en-us/create/functions/install-chocolateypackage +## - https://docs.chocolatey.org/en-us/create/functions/install-chocolateyinstallpackage +## add additional optional arguments as necessary +##Install-ChocolateyPackage $packageName $fileType $silentArgs $url [$url64 -validExitCodes $validExitCodes -checksum $checksum -checksumType $checksumType -checksum64 $checksum64 -checksumType64 $checksumType64] + +## Download and unpack a zip file - https://docs.chocolatey.org/en-us/create/functions/install-chocolateyzippackage +##Install-ChocolateyZipPackage $packageName $url $toolsDir [$url64 -checksum $checksum -checksumType $checksumType -checksum64 $checksum64 -checksumType64 $checksumType64] + +## Install Visual Studio Package - https://docs.chocolatey.org/en-us/create/functions/install-chocolateyvsixpackage +#Install-ChocolateyVsixPackage $packageName $url [$vsVersion] [-checksum $checksum -checksumType $checksumType] +#Install-ChocolateyVsixPackage @packageArgs + +## see the full list at https://docs.chocolatey.org/en-us/create/functions + +## downloader that the main helpers use to download items +## if removing $url64, please remove from here +## - https://docs.chocolatey.org/en-us/create/functions/get-chocolateywebfile +#Get-ChocolateyWebFile $packageName 'DOWNLOAD_TO_FILE_FULL_PATH' $url $url64 + +## Installer, will assert administrative rights - used by Install-ChocolateyPackage +## use this for embedding installers in the package when not going to community feed or when you have distribution rights +## - https://docs.chocolatey.org/en-us/create/functions/install-chocolateyinstallpackage +#Install-ChocolateyInstallPackage $packageName $fileType $silentArgs '_FULLFILEPATH_' -validExitCodes $validExitCodes + +## Unzips a file to the specified location - auto overwrites existing content +## - https://docs.chocolatey.org/en-us/create/functions/get-chocolateyunzip +#Get-ChocolateyUnzip "FULL_LOCATION_TO_ZIP.zip" $toolsDir + +## Runs processes asserting UAC, will assert administrative rights - used by Install-ChocolateyInstallPackage +## - https://docs.chocolatey.org/en-us/create/functions/start-chocolateyprocessasadmin +#Start-ChocolateyProcessAsAdmin 'STATEMENTS_TO_RUN' 'Optional_Application_If_Not_PowerShell' -validExitCodes $validExitCodes + +## To avoid quoting issues, you can also assemble your -Statements in another variable and pass it in +#$appPath = "$env:ProgramFiles\appname" +##Will resolve to C:\Program Files\appname +#$statementsToRun = "/C `"$appPath\bin\installservice.bat`"" +#Start-ChocolateyProcessAsAdmin $statementsToRun cmd -validExitCodes $validExitCodes + +## add specific folders to the path - any executables found in the chocolatey package +## folder will already be on the path. This is used in addition to that or for cases +## when a native installer doesn't add things to the path. +## - https://docs.chocolatey.org/en-us/create/functions/install-chocolateypath +#Install-ChocolateyPath 'LOCATION_TO_ADD_TO_PATH' 'User_OR_Machine' # Machine will assert administrative rights + +## Add specific files as shortcuts to the desktop +## - https://docs.chocolatey.org/en-us/create/functions/install-chocolateyshortcut +#$target = Join-Path $toolsDir "$($packageName).exe" +# Install-ChocolateyShortcut -shortcutFilePath "" -targetPath "" [-workDirectory "C:\" -arguments "C:\test.txt" -iconLocation "C:\test.ico" -description "This is the description"] + +## Outputs the bitness of the OS (either "32" or "64") +## - https://docs.chocolatey.org/en-us/create/functions/get-osarchitecturewidth +#$osBitness = Get-ProcessorBits + +## Set persistent Environment variables +## - https://docs.chocolatey.org/en-us/create/functions/install-chocolateyenvironmentvariable +#Install-ChocolateyEnvironmentVariable -variableName "SOMEVAR" -variableValue "value" [-variableType = 'Machine' #Defaults to 'User'] + +## Set up a file association +## - https://docs.chocolatey.org/en-us/create/functions/install-chocolateyfileassociation +#Install-ChocolateyFileAssociation + +## Adding a shim when not automatically found - Chocolatey automatically shims exe files found in package directory. +## - https://docs.chocolatey.org/en-us/create/functions/install-binfile +## - https://docs.chocolatey.org/en-us/create/create-packages#how-do-i-exclude-executables-from-getting-shims +#Install-BinFile + +##PORTABLE EXAMPLE +#$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)" +# despite the name "Install-ChocolateyZipPackage" this also works with 7z archives +#Install-ChocolateyZipPackage $packageName $url $toolsDir $url64 +## END PORTABLE EXAMPLE diff --git a/automatic/cyberghost-vpn/tools/chocolateyuninstall.ps1 b/automatic/cyberghost-vpn/tools/chocolateyuninstall.ps1 new file mode 100644 index 000000000..430364fbd --- /dev/null +++ b/automatic/cyberghost-vpn/tools/chocolateyuninstall.ps1 @@ -0,0 +1,78 @@ +# IMPORTANT: Before releasing this package, copy/paste the next 2 lines into PowerShell to remove all comments from this file: +# $f='c:\path\to\thisFile.ps1' +# gc $f | ? {$_ -notmatch "^\s*#"} | % {$_ -replace '(^.*?)\s*?[^``]#.*','$1'} | Out-File $f+".~" -en utf8; mv -fo $f+".~" $f + +## NOTE: In 80-90% of the cases (95% with licensed versions due to Package Synchronizer and other enhancements), +## AutoUninstaller should be able to detect and handle registry uninstalls without a chocolateyUninstall.ps1. +## See https://docs.chocolatey.org/en-us/choco/commands/uninstall +## and https://docs.chocolatey.org/en-us/create/functions/uninstall-chocolateypackage + +## If this is an MSI, ensure 'softwareName' is appropriate, then clean up comments and you are done. +## If this is an exe, change fileType, silentArgs, and validExitCodes + +$ErrorActionPreference = 'Stop' # stop on all errors +$packageArgs = @{ + packageName = $env:ChocolateyPackageName + softwareName = 'cyberghost-vpn*' #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique + fileType = 'EXE_MSI_OR_MSU' #only one of these: MSI or EXE (ignore MSU for now) + # MSI + silentArgs = "/qn /norestart" + validExitCodes= @(0, 3010, 1605, 1614, 1641) # https://msdn.microsoft.com/en-us/library/aa376931(v=vs.85).aspx + # OTHERS + # Uncomment matching EXE type (sorted by most to least common) + #silentArgs = '/S' # NSIS + #silentArgs = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-' # Inno Setup + #silentArgs = '/s' # InstallShield + #silentArgs = '/s /v"/qn"' # InstallShield with MSI + #silentArgs = '/s' # Wise InstallMaster + #silentArgs = '-s' # Squirrel + #silentArgs = '-q' # Install4j + #silentArgs = '-s -u' # Ghost + # Note that some installers, in addition to the silentArgs above, may also need assistance of AHK to achieve silence. + #silentArgs = '' # none; make silent with input macro script like AutoHotKey (AHK) + # https://community.chocolatey.org/packages/autohotkey.portable + #validExitCodes= @(0) #please insert other valid exit codes here +} + +[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName'] + +if ($key.Count -eq 1) { + $key | % { + $packageArgs['file'] = "$($_.UninstallString)" #NOTE: You may need to split this if it contains spaces, see below + + if ($packageArgs['fileType'] -eq 'MSI') { + # The Product Code GUID is all that should be passed for MSI, and very + # FIRST, because it comes directly after /x, which is already set in the + # Uninstall-ChocolateyPackage msiargs (facepalm). + $packageArgs['silentArgs'] = "$($_.PSChildName) $($packageArgs['silentArgs'])" + + # Don't pass anything for file, it is ignored for msi (facepalm number 2) + # Alternatively if you need to pass a path to an msi, determine that and + # use it instead of the above in silentArgs, still very first + $packageArgs['file'] = '' + } else { + # NOTES: + # - You probably will need to sanitize $packageArgs['file'] as it comes from the registry and could be in a variety of fun but unusable formats + # - Split args from exe in $packageArgs['file'] and pass those args through $packageArgs['silentArgs'] or ignore them + # - Ensure you don't pass double quotes in $file (aka $packageArgs['file']) - otherwise you will get "Illegal characters in path when you attempt to run this" + # - Review the code for auto-uninstaller for all of the fun things it does in sanitizing - https://github.com/chocolatey/choco/blob/bfe351b7d10c798014efe4bfbb100b171db25099/src/chocolatey/infrastructure.app/services/AutomaticUninstallerService.cs#L142-L192 + } + + Uninstall-ChocolateyPackage @packageArgs + } +} elseif ($key.Count -eq 0) { + Write-Warning "$packageName has already been uninstalled by other means." +} elseif ($key.Count -gt 1) { + Write-Warning "$($key.Count) matches found!" + Write-Warning "To prevent accidental data loss, no programs will be uninstalled." + Write-Warning "Please alert package maintainer the following keys were matched:" + $key | % {Write-Warning "- $($_.DisplayName)"} +} + +## OTHER POWERSHELL FUNCTIONS +## https://docs.chocolatey.org/en-us/create/functions +#Uninstall-ChocolateyZipPackage $packageName # Only necessary if you did not unpack to package directory - see https://docs.chocolatey.org/en-us/create/functions/uninstall-chocolateyzippackage +#Uninstall-ChocolateyEnvironmentVariable - https://docs.chocolatey.org/en-us/create/functions/uninstall-chocolateyenvironmentvariable +#Uninstall-BinFile # Only needed if you used Install-BinFile - see https://docs.chocolatey.org/en-us/create/functions/uninstall-binfile +## Remove any shortcuts you added in the install script. +