Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community.
Moderation
Every version of each package undergoes a rigorous moderation process before it goes live that typically includes:
- Security, consistency, and quality checking
- Installation testing
- Virus checking through VirusTotal
- Human moderators who give final review and sign off
More detail at Security and Moderation.
Organizational Use
If you are an organization using Chocolatey, we want your experience to be fully reliable. Due to the nature of this publicly offered repository, reliability cannot be guaranteed. Packages offered here are subject to distribution rights, which means they may need to reach out further to the internet to the official locations to download files at runtime.
Fortunately, distribution rights do not apply for internal use. With any edition of Chocolatey (including the free open source edition), you can host your own packages and cache or internalize existing community packages.
Disclaimer
Your use of the packages on this site means you understand they are not supported or guaranteed in any way. Learn more...
-
STEP1
Package Review
-
STEP2
Integration Method
-
STEP3
Internal Repo Url
-
STEP4
Environment Setup
-
STEP5
Install Script
Step 1: Review Your Packages
Step 2: Choose Your Integration Method
Step 3: Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
Step 3: Copy Your Script or Download Config
Option 1: Copy Script
Option 2: Download Config
Step 4: Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
-
You can also just download the packages and push them to a repository
Download Packages
-
Open Source
-
Download the packages:
Download Packages - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
-
For package and dependencies run:
- Automate package internalization
-
Run: (additional options)
Step 5: Copy Your Script
See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.
### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
#### generally really quick to set up and there are quite a few options.
#### Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
#### are repository servers and will give you the ability to manage multiple
#### repositories and types from one server installation.
### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
#### Please see https://chocolatey.org/install#organization
### c. Other Requirements ###
#### We initialize a few things that are needed by this script - there are no other requirements.
$ErrorActionPreference = "Stop"
#### Set TLS 1.2 (3072) as that is the minimum required by various up-to-date repositories.
#### Use integers because the enumeration value for TLS 1.2 won't exist
#### in .NET 4.0, even though they are addressable if .NET 4.5+ is
#### installed (.NET 4.5 is an in-place upgrade).
[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072
#### We use this variable for future REST calls.
$RequestArguments = @{
UseBasicParsing = $true
}
## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
#### Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$NugetRepositoryUrl = "INTERNAL REPO URL"
### b. Internal Repository Credential ###
#### If required, add the repository access credential here
# $NugetRepositoryCredential = [PSCredential]::new(
# "username",
# ("password" | ConvertTo-SecureString -AsPlainText -Force)
# )
# $RequestArguments.Credential = $NugetRepositoryCredential
### c. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it
$ChocolateyDownloadUrl = "$($NugetRepositoryUrl.TrimEnd('/'))/package/chocolatey.1.1.0.nupkg"
### d. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService"
#### ii. If using a Client Salt, add it here
# $ChocolateyCentralManagementClientSalt = "clientsalt"
#### iii. If using a Service Salt, add it here
# $ChocolateyCentralManagementServiceSalt = "servicesalt"
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
#### Download the Nupkg, appending .zip to the filename to handle archive cmdlet limitations
if (-not (Get-Command choco.exe -ErrorAction SilentlyContinue)) {
$TempDirectory = Join-Path $env:Temp "chocolateyInstall"
if (-not (Test-Path $TempDirectory -PathType Container)) {
$null = New-Item -Path $TempDirectory -ItemType Directory
}
$DownloadedNupkg = Join-Path $TempDirectory "$(Split-Path $ChocolateyDownloadUrl -Leaf).zip"
Invoke-WebRequest -Uri $ChocolateyDownloadUrl -OutFile $DownloadedNupkg @RequestArguments
#### Extract the Nupkg, and run the chocolateyInstall script
if (Get-Command Microsoft.PowerShell.Archive\Expand-Archive -ErrorAction SilentlyContinue) {
Microsoft.PowerShell.Archive\Expand-Archive -Path $DownloadedNupkg -DestinationPath $TempDirectory -Force
} else {
# PowerShell versions <4.0 do not have this function available
try {
$shellApplication = New-Object -ComObject Shell.Application
$zipPackage = $shellApplication.NameSpace($DownloadedNupkg)
$destinationFolder = $shellApplication.NameSpace($TempDirectory)
$destinationFolder.CopyHere($zipPackage.Items(), 0x10)
} catch {
Write-Warning "Unable to unzip package using built-in compression."
throw $_
}
}
& $(Join-Path $TempDirectory "tools\chocolateyInstall.ps1")
}
if (-not (Get-Command choco.exe -ErrorAction SilentlyContinue)) {
refreshenv
}
## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# choco feature enable -n useFipsCompliantChecksums
### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
choco config set --name cacheLocation --value C:\ProgramData\chocolatey\cache
#### Increase timeout to at least 4 hours
choco config set --name commandExecutionTimeoutSeconds --value 14400
#### Turn off download progress when running choco through integrations
choco feature disable --name showDownloadProgress
### c. Sources ###
#### Remove the default community package repository source
choco source list --limitoutput | ConvertFrom-Csv -Header 'Name', 'Location' -Delimiter '|' | ForEach-Object {
if ($_.Location -eq 'https://community.chocolatey.org/api/v2/') {
choco source remove -n $_.Name
}
}
#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE may require changes
if ($NugetRepositoryCredential) {
choco source add --name ChocolateyInternal --source $NugetRepositoryUrl --user $NugetRepositoryCredential.UserName --password $NugetRepositoryCredential.GetNetworkCredential().Password --priority 1
} else {
choco source add --name ChocolateyInternal --source $NugetRepositoryUrl --priority 1
}
### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
#### to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
#### when you browse to https://community.chocolatey.org/api/v2/
choco upgrade chocolatey --confirm
## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
choco install chocolatey-license --source $NugetRepositoryUrl --confirm
### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
if ("chocolatey-license" -in (choco list --localonly --limitoutput | ConvertFrom-Csv -Header "Name" -Delimiter "|").Name) {
choco source disable --name chocolatey.licensed
} else {
Write-Warning "Not disabling 'chocolatey.licensed' feed, as Chocolatey-License has not been installed."
}
### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.
#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
if ("chocolatey-license" -in (choco list --localonly --limitoutput | ConvertFrom-Csv -Header "Name" -Delimiter "|").Name) {
choco install chocolatey.extension --source $NugetRepositoryUrl --confirm
} else {
Write-Warning "Not installing 'chocolatey.extension', as Chocolatey-License has not been installed."
}
#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/
### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
choco feature disable --name showNonElevatedWarnings
choco feature enable --name useBackgroundService
choco feature enable --name useBackgroundServiceWithNonAdministratorsOnly
choco feature enable --name allowBackgroundServiceUninstallsFromUserInstallsOnly
choco config set --name allowedBackgroundServiceCommands --value "install,upgrade,uninstall"
### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if ($ChocolateyCentralManagementUrl) {
choco install chocolatey-agent --source $NugetRepositoryUrl --confirm
choco config set --name CentralManagementServiceUrl --value $ChocolateyCentralManagementUrl
if ($ChocolateyCentralManagementClientSalt) {
choco config set --name centralManagementClientCommunicationSaltAdditivePassword --value $ChocolateyCentralManagementClientSalt
}
if ($ChocolateyCentralManagementServiceSalt) {
choco config set --name centralManagementServiceCommunicationSaltAdditivePassword --value $ChocolateyCentralManagementServiceSalt
}
choco feature enable --name useChocolateyCentralManagement
choco feature enable --name useChocolateyCentralManagementDeployments
}
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
If Applicable - Chocolatey Configuration/Installation
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.
### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
#### generally really quick to set up and there are quite a few options.
#### Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
#### are repository servers and will give you the ability to manage multiple
#### repositories and types from one server installation.
### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
#### Please see https://chocolatey.org/install#organization
### c. Other Requirements ###
#### i. chocolatey.chocolatey
##### You will require the chocolatey.chocolatey collection to be installed
##### on all machines using this playbook.
##### Please see https://github.com/chocolatey/chocolatey-ansible/#installing-the-collection-from-ansible-galaxy
- name: Install and Configure Chocolatey
hosts: all
## 2. TOP LEVEL VARIABLES ##
vars:
### a. Your internal repository url (the main one). ###
#### Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
nuget_repository_url: INTERNAL REPO URL
### b. Internal Repository Credential ###
#### If required, add the repository access credential here and
#### uncomment lines with source_username and source_password below
# nuget_repository_username: username
# nuget_repository_password: password
### c. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# chocolatey_central_management_url: https://chocolatey-central-management:24020/ChocolateyManagementService
#### ii. If using a Client Salt, add it here
# chocolatey_central_management_client_salt: clientsalt
#### iii. If using a Service Salt, add it here
# chocolatey_central_management_service_salt: servicesalt
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
tasks:
- name: Install chocolatey
win_chocolatey:
name: chocolatey
source: {{ nuget_repository_url }}
# source_username: {{ nuget_repository_username }}
# source_password: {{ nuget_repository_password }}
## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# - name: Enable FIPS compliance
# win_chocolatey_feature:
# name: useFipsCompliantChecksums
# state: enabled
### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
- name: Set the cache location
win_chocolatey_config:
name: cacheLocation
state: present
value: C:\ProgramData\chocolatey\cache
#### Increase timeout to at least 4 hours
- name: Set the command execution timeout
win_chocolatey_config:
name: commandExecutionTimeoutSeconds
state: present
value: 14400
#### Turn off download progress when running choco through integrations
- name: Disable showing download progress
win_chocolatey_feature:
name: showDownloadProgress
state: disabled
### c. Sources ###
#### Remove the default community package repository source
- name: Remove Chocolatey Community Repository
win_chocolatey_source:
name: chocolatey
state: absent
#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE may require changes
- name: Add Internal Repository
win_chocolatey_source:
name: ChocolateyInternal
state: present
source: {{ nuget_repository_url }}
# source_username: {{ nuget_repository_username }}
# source_password: {{ nuget_repository_password }}
priority: 1
### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
#### to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
#### when you browse to https://community.chocolatey.org/api/v2/
- name: Upgrade Chocolatey
win_chocolatey:
name: chocolatey
state: latest
## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
- name: Install Chocolatey License
win_chocolatey:
name: chocolatey-license
source: ChocolateyInternal
state: latest
### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
- name: Disable Chocolatey Community Repository
win_chocolatey_source:
name: chocolatey.licensed
state: disabled
### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.
#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
- name: Install Chocolatey Extension
win_chocolatey:
name: chocolatey.extension
source: ChocolateyInternal
state: latest
#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/
### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
- name: Hide not-elevated warnings
win_chocolatey_feature:
name: showNonElevatedWarnings
state: disabled
- name: Use background mode for self-service
win_chocolatey_feature:
name: useBackgroundService
state: enabled
- name: Use background service for non-admins
win_chocolatey_feature:
name: useBackgroundServiceWithNonAdministratorsOnly
state: enabled
- name: Allow background uninstallation for user installs
win_chocolatey_feature:
name: allowBackgroundServiceUninstallsFromUserInstallsOnly
state: enabled
- name: Set allowed background service commands
win_chocolatey_config:
name: backgroundServiceAllowedCommands
state: present
value: install,upgrade,uninstall
### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
- name: Install Chocolatey Agent
when: chocolatey_central_management_url is defined
win_chocolatey:
name: chocolatey-agent
source: ChocolateyInternal
state: latest
- name: Set the Central Management Service URL
when: chocolatey_central_management_url is defined
win_chocolatey_config:
name: CentralManagementServiceUrl
state: present
value: {{ chocolatey_central_management_url }}
- name: Set the Central Management Client Salt
when: chocolatey_central_management_client_salt is defined
win_chocolatey_config:
name: centralManagementClientCommunicationSaltAdditivePassword
state: present
value: {{ chocolatey_central_management_client_salt }}
- name: Set the Central Management Service Salt
when: chocolatey_central_management_service_salt is defined
win_chocolatey_config:
name: centralManagementServiceCommunicationSaltAdditivePassword
state: present
value: {{ chocolatey_central_management_service_salt }}
- name: Use Central Management
when: chocolatey_central_management_url is defined
win_chocolatey_feature:
name: useChocolateyCentralManagement
state: enabled
- name: Use Central Management Deployments
when: chocolatey_central_management_url is defined
win_chocolatey_feature:
name: useChocolateyCentralManagementDeployments
state: enabled
See docs at https://docs.chef.io/resource_chocolatey_package.html.
If Applicable - Chocolatey Configuration/Installation
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.
### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
#### generally really quick to set up and there are quite a few options.
#### Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
#### are repository servers and will give you the ability to manage multiple
#### repositories and types from one server installation.
### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
#### Please see https://chocolatey.org/install#organization
### c. Other Requirements ###
#### The Chocolatey resources are available with any recent version of Chef.
#### We utilise the Chocolatey recipe to install the Chocolatey binaries.
include_recipe "chocolatey"
## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
#### Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
NugetRepositoryUrl = "INTERNAL REPO URL"
### b. Internal Repository Credential ###
#### If required, add the repository access credential here
# NugetRepositoryUsername = "username"
# NugetRepositoryPassword = "password"
### c. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
ChocolateyNupkgUrl = "INTERNAL REPO URL/package/chocolatey.1.1.0.nupkg",
### d. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService"
#### ii. If using a Client Salt, add it here
# ChocolateyCentralManagementClientSalt = "clientsalt"
#### iii. If using a Service Salt, add it here
# ChocolateyCentralManagementServiceSalt = "servicesalt"
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
node['chocolatey']['install vars'] = {
'chocolateyDownloadUrl' => "#{ChocolateyNupkgUrl}",
}
## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# chocolatey_feature 'useFipsCompliantChecksums' do
# action :enable
# end
### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
chocolatey_config 'cacheLocation' do
value 'C:\ProgramData\chocolatey\cache'
end
#### Increase timeout to at least 4 hours
chocolatey_config 'commandExecutionTimeoutSeconds' do
value '14400'
end
#### Turn off download progress when running choco through integrations
chocolatey_feature 'showDownloadProgress' do
action :disable
end
### c. Sources ###
#### Remove the default community package repository source
chocolatey_source 'chocolatey' do
action :remove
end
#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE may require changes
chocolatey_source 'ChocolateyInternal' do
source "#{NugetRepositoryUrl}"
priority 1
action :add
end
execute 'ChocolateyInternal' do
command "choco source add --name ChocolateyInternal -s #{NugetRepositoryUrl} -u=#{NugetRepositoryUsername} -p=#{NugetRepositoryPassword} --priority=1"
only_if { NugetRepositoryUsername != nil || NugetRepositoryPassword != nil }
end
### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
#### to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
#### when you browse to https://community.chocolatey.org/api/v2/
chocolatey_package 'chocolatey' do
action :upgrade
source "#{NugetRepositoryUrl}"
end
## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
chocolatey_package 'chocolatey-license' do
action :install
source "#{NugetRepositoryUrl}"
end
### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
chocolatey_source 'chocolatey.licensed' do
action :disable
end
### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.
#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
chocolatey_package 'chocolatey.extention' do
action install
source "#{NugetRepositoryUrl}"
end
#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/
### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
chocolatey_feature 'showNonElevatedWarnings' do
action :disable
end
chocolatey_feature 'useBackgroundService' do
action :enable
end
chocolatey_feature 'useBackgroundServiceWithNonAdministratorsOnly' do
action :enable
end
chocolatey_feature 'allowBackgroundServiceUninstallsFromUserInstallsOnly' do
action :enable
end
chocolatey_config 'backgroundServiceAllowedCommands' do
value 'install,upgrade,uninstall'
end
### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
chocolatey_package 'chocolatey-agent' do
action install
source "#{NugetRepositoryUrl}"
# user "#{NugetRepositoryUsername}"
# password "#{NugetRepositoryPassword}"
only_if { ChocolateyCentralManagementUrl != nil }
end
chocolatey_config 'CentralManagementServiceUrl' do
value "#{ChocolateyCentralManagementUrl}"
only_if { ChocolateyCentralManagementUrl != nil }
end
chocolatey_config 'centralManagementClientCommunicationSaltAdditivePassword' do
value "#{ChocolateyCentralManagementClientSalt}"
only_if { ChocolateyCentralManagementClientSalt != nil }
end
chocolatey_config 'centralManagementServiceCommunicationSaltAdditivePassword' do
value "#{ChocolateyCentralManagementServiceSalt}"
only_if { ChocolateyCentralManagementServiceSalt != nil }
end
chocolatey_feature 'useChocolateyCentralManagement' do
action :enable
only_if { ChocolateyCentralManagementUrl != nil }
end
chocolatey_feature 'useChocolateyCentralManagementDeployments' do
action :enable
only_if { ChocolateyCentralManagementUrl != nil }
end
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
If Applicable - Chocolatey Configuration/Installation
#requires -Modules cChoco
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.
### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
#### generally really quick to set up and there are quite a few options.
#### Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
#### are repository servers and will give you the ability to manage multiple
#### repositories and types from one server installation.
### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
#### Please see https://chocolatey.org/install#organization
### c. Other Requirements ###
#### i. Requires chocolatey\cChoco DSC module to be installed on the machine compiling the DSC manifest
#### NOTE: This will need to be installed before running the DSC portion of this script
if (-not (Get-Module cChoco -ListAvailable)) {
$null = Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
if (($PSGallery = Get-PSRepository -Name PSGallery).InstallationPolicy -ne "Trusted") {
Set-PSRepository -Name PSGallery -InstallationPolicy Trusted
}
Install-Module -Name cChoco
if ($PSGallery.InstallationPolicy -ne "Trusted") {
Set-PSRepository -Name PSGallery -InstallationPolicy $PSGallery.InstallationPolicy
}
}
#### ii. Requires a hosted copy of the install.ps1 script
##### This should be available to download without authentication.
##### The original script can be found here: https://community.chocolatey.org/install.ps1
Configuration ChocolateyConfig {
## 2. TOP LEVEL VARIABLES ##
param(
### a. Your internal repository url (the main one). ###
#### Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$NugetRepositoryUrl = "INTERNAL REPO URL",
### b. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
$ChocolateyNupkgUrl = "INTERNAL REPO URL/package/chocolatey.1.1.0.nupkg",
### c. Internal Repository Credential ###
#### If required, add the repository access credential here
# $NugetRepositoryCredential = [PSCredential]::new(
# "username",
# ("password" | ConvertTo-SecureString -AsPlainText -Force)
# ),
### d. Install.ps1 URL
#### The path to the hosted install script:
$ChocolateyInstallPs1Url = "https://community.chocolatey.org/install.ps1"
### e. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService",
#### ii. If using a Client Salt, add it here
# $ChocolateyCentralManagementClientSalt = "clientsalt",
#### iii. If using a Service Salt, add it here
# $ChocolateyCentralManagementServiceSalt = "servicesalt"
)
Import-DscResource -ModuleName PSDesiredStateConfiguration
Import-DscResource -ModuleName cChoco
Node 'localhost' {
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
Environment chocoDownloadUrl {
Name = "chocolateyDownloadUrl"
Value = $ChocolateyNupkgUrl
}
cChocoInstaller installChocolatey {
DependsOn = "[Environment]chocoDownloadUrl"
InstallDir = Join-Path $env:ProgramData "chocolatey"
ChocoInstallScriptUrl = $ChocolateyInstallPs1Url
}
## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# cChocoFeature featureFipsCompliance {
# FeatureName = "useFipsCompliantChecksums"
# }
### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
cChocoConfig cacheLocation {
DependsOn = "[cChocoInstaller]installChocolatey"
ConfigName = "cacheLocation"
Value = "C:\ProgramData\chocolatey\cache"
}
#### Increase timeout to at least 4 hours
cChocoConfig commandExecutionTimeoutSeconds {
DependsOn = "[cChocoInstaller]installChocolatey"
ConfigName = "commandExecutionTimeoutSeconds"
Value = 14400
}
#### Turn off download progress when running choco through integrations
cChocoFeature showDownloadProgress {
DependsOn = "[cChocoInstaller]installChocolatey"
FeatureName = "showDownloadProgress"
Ensure = "Absent"
}
### c. Sources ###
#### Remove the default community package repository source
cChocoSource removeCommunityRepository {
DependsOn = "[cChocoInstaller]installChocolatey"
Name = "chocolatey"
Ensure = "Absent"
}
#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here.
#### NOTE: This EXAMPLE may require changes
cChocoSource addInternalSource {
DependsOn = "[cChocoInstaller]installChocolatey"
Name = "ChocolateyInternal"
Source = $NugetRepositoryUrl
Credentials = $NugetRepositoryCredential
Priority = 1
}
### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
#### to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
#### when you browse to https://community.chocolatey.org/api/v2/
cChocoPackageInstaller updateChocolatey {
DependsOn = "[cChocoSource]addInternalSource", "[cChocoSource]removeCommunityRepository"
Name = "chocolatey"
AutoUpgrade = $true
}
## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
cChocoPackageInstaller chocolateyLicense {
DependsOn = "[cChocoPackageInstaller]updateChocolatey"
Name = "chocolatey-license"
}
### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
Script disableLicensedSource {
DependsOn = "[cChocoPackageInstaller]chocolateyLicense"
GetScript = {
$Source = choco source list --limitoutput | `
ConvertFrom-Csv -Delimiter '|' -Header Name, Source, Disabled | `
Where-Object Name -eq "chocolatey.licensed"
return @{
Result = if ($Source) {
[bool]::Parse($Source.Disabled)
} else {
Write-Warning "Source 'chocolatey.licensed' was not present."
$true # Source does not need disabling
}
}
}
SetScript = {
$null = choco source disable --name "chocolatey.licensed"
}
TestScript = {
$State = [ScriptBlock]::Create($GetScript).Invoke()
return $State.Result
}
}
### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.
#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
cChocoPackageInstaller chocolateyLicensedExtension {
DependsOn = "[Script]disableLicensedSource"
Name = "chocolatey.extension"
}
#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/
### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
cChocoFeature hideElevatedWarnings {
DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
FeatureName = "showNonElevatedWarnings"
Ensure = "Absent"
}
cChocoFeature useBackgroundService {
DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
FeatureName = "useBackgroundService"
Ensure = "Present"
}
cChocoFeature useBackgroundServiceWithNonAdmins {
DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
FeatureName = "useBackgroundServiceWithNonAdministratorsOnly"
Ensure = "Present"
}
cChocoFeature useBackgroundServiceUninstallsForUserInstalls {
DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
FeatureName = "allowBackgroundServiceUninstallsFromUserInstallsOnly"
Ensure = "Present"
}
cChocoConfig allowedBackgroundServiceCommands {
DependsOn = "[cChocoFeature]useBackgroundService"
ConfigName = "backgroundServiceAllowedCommands"
Value = "install,upgrade,uninstall"
}
### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if ($ChocolateyCentralManagementUrl) {
cChocoPackageInstaller chocolateyAgent {
DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
Name = "chocolatey-agent"
}
cChocoConfig centralManagementServiceUrl {
DependsOn = "[cChocoPackageInstaller]chocolateyAgent"
ConfigName = "CentralManagementServiceUrl"
Value = $ChocolateyCentralManagementUrl
}
if ($ChocolateyCentralManagementClientSalt) {
cChocoConfig centralManagementClientSalt {
DependsOn = "[cChocoPackageInstaller]chocolateyAgent"
ConfigName = "centralManagementClientCommunicationSaltAdditivePassword"
Value = $ChocolateyCentralManagementClientSalt
}
}
if ($ChocolateyCentralManagementServiceSalt) {
cChocoConfig centralManagementServiceSalt {
DependsOn = "[cChocoPackageInstaller]chocolateyAgent"
ConfigName = "centralManagementServiceCommunicationSaltAdditivePassword"
Value = $ChocolateyCentralManagementServiceSalt
}
}
cChocoFeature useCentralManagement {
DependsOn = "[cChocoPackageInstaller]chocolateyAgent"
FeatureName = "useChocolateyCentralManagement"
Ensure = "Present"
}
cChocoFeature useCentralManagementDeployments {
DependsOn = "[cChocoPackageInstaller]chocolateyAgent"
FeatureName = "useChocolateyCentralManagementDeployments"
Ensure = "Present"
}
}
}
}
# If working this into an existing configuration with a good method for
$ConfigData = @{
AllNodes = @(
@{
NodeName = "localhost"
PSDscAllowPlainTextPassword = $true
}
)
}
try {
Push-Location $env:Temp
$Config = ChocolateyConfig -ConfigurationData $ConfigData
Start-DscConfiguration -Path $Config.PSParentPath -Wait -Verbose -Force
} finally {
Pop-Location
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
If Applicable - Chocolatey Configuration/Installation
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.
### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
#### generally really quick to set up and there are quite a few options.
#### Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
#### are repository servers and will give you the ability to manage multiple
#### repositories and types from one server installation.
### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
#### Please see https://chocolatey.org/install#organization
### c. Other Requirements ###
#### i. Requires puppetlabs/chocolatey module
#### See https://forge.puppet.com/puppetlabs/chocolatey
## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
#### Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$_repository_url = 'INTERNAL REPO URL'
### b. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
$_choco_download_url = 'INTERNAL REPO URL/package/chocolatey.1.1.0.nupkg'
### c. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $_chocolatey_central_management_url = 'https://chocolatey-central-management:24020/ChocolateyManagementService'
#### ii. If using a Client Salt, add it here
# $_chocolatey_central_management_client_salt = "clientsalt"
#### iii. If using a Service Salt, add it here
# $_chocolatey_central_management_service_salt = 'servicesalt'
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
### Note: `chocolatey_download_url is completely different than normal
### source locations. This is directly to the bare download url for the
### chocolatey.nupkg, similar to what you see when you browse to
### https://community.chocolatey.org/api/v2/package/chocolatey
class {'chocolatey':
chocolatey_download_url => $_choco_download_url,
use_7zip => false,
}
## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
#chocolateyfeature {'useFipsCompliantChecksums':
# ensure => enabled,
#}
### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
chocolateyconfig {'cacheLocation':
value => 'C:\ProgramData\chocolatey\cache',
}
#### Increase timeout to at least 4 hours
chocolateyconfig {'commandExecutionTimeoutSeconds':
value => '14400',
}
#### Turn off download progress when running choco through integrations
chocolateyfeature {'showDownloadProgress':
ensure => disabled,
}
### c. Sources ###
#### Remove the default community package repository source
chocolateysource {'chocolatey':
ensure => absent,
location => 'https://community.chocolatey.org/api/v2/',
}
#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE requires changes
chocolateysource {'internal_chocolatey':
ensure => present,
location => $_repository_url,
priority => 1,
username => 'optional',
password => 'optional,not ensured',
bypass_proxy => true,
admin_only => false,
allow_self_service => false,
}
### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
#### to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
#### when you browse to https://community.chocolatey.org/api/v2/
package {'chocolatey':
ensure => latest,
provider => chocolatey,
source => $_repository_url,
}
## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/guides/organizations/organizational-deployment-guide#exercise-4-create-a-package-for-the-license
# TODO: Add resource for installing/ensuring the chocolatey-license package
package {'chocolatey-license':
ensure => latest,
provider => chocolatey,
source => $_repository_url,
}
### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
## Disabled sources still need all other attributes until
## https://tickets.puppetlabs.com/browse/MODULES-4449 is resolved.
## Password is necessary with user, but not ensurable, so it should not
## matter what it is set to here. If you ever do get into trouble here,
## the password is your license GUID.
chocolateysource {'chocolatey.licensed':
ensure => disabled,
priority => '10',
user => 'customer',
password => '1234',
require => Package['chocolatey-license'],
}
### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.
#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
package {'chocolatey.extension':
ensure => latest,
provider => chocolatey,
source => $_repository_url,
require => Package['chocolatey-license'],
}
#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/
### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
chocolateyfeature {'showNonElevatedWarnings':
ensure => disabled,
}
chocolateyfeature {'useBackgroundService':
ensure => enabled,
}
chocolateyfeature {'useBackgroundServiceWithNonAdministratorsOnly':
ensure => enabled,
}
chocolateyfeature {'allowBackgroundServiceUninstallsFromUserInstallsOnly':
ensure => enabled,
}
chocolateyconfig {'backgroundServiceAllowedCommands':
value => 'install,upgrade,uninstall',
}
### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if $_chocolatey_central_management_url {
package {'chocolatey-agent':
ensure => latest,
provider => chocolatey,
source => $_repository_url,
require => Package['chocolatey-license'],
}
chocolateyconfig {'CentralManagementServiceUrl':
value => $_chocolatey_central_management_url,
}
if $_chocolatey_central_management_client_salt {
chocolateyconfig {'centralManagementClientCommunicationSaltAdditivePassword':
value => $_chocolatey_central_management_client_salt,
}
}
if $_chocolatey_central_management_service_salt {
chocolateyconfig {'centralManagementClientCommunicationSaltAdditivePassword':
value => $_chocolatey_central_management_client_salt,
}
}
chocolateyfeature {'useChocolateyCentralManagement':
ensure => enabled,
require => Package['chocolatey-agent'],
}
chocolateyfeature {'useChocolateyCentralManagementDeployments':
ensure => enabled,
require => Package['chocolatey-agent'],
}
}
Need Help? View our docs or file an issue.
There is already a version of this package in your Script Builder
Current Version | New Version |
---|---|
- Passing
- Failing
- Pending
- Unknown / Exempted

Downloads:
56,896
Downloads of v 8.1.0297:
168
Last Update:
20 Aug 2018
Package Maintainer(s):
Software Author(s):
- Build: TuxProject.de
- Developer: vim team
Tags:
vim-tux vim editor tux
Vim Tux (Portable)
This is not the latest version of Vim Tux (Portable) available.
- 1
- 2
- 3
8.1.0297 | Updated: 20 Aug 2018
Downloads:
56,896
Downloads of v 8.1.0297:
168
Maintainer(s):
Software Author(s):
- Build: TuxProject.de
- Developer: vim team
Edit Package
To edit the metadata for a package, please upload an updated version of the package.
Chocolatey's Community Package Repository currently does not allow updating package metadata on the website. This helps ensure that the package itself (and the source used to build the package) remains the one true source of package metadata.
This does require that you increment the package version.
- 1
- 2
- 3
Vim Tux (Portable)
8.1.0297
This is not the latest version of Vim Tux (Portable) available.
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
Validation Testing Passed
Verification Testing Passed
DetailsScan Testing Resulted in Flagged:
This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.
We recommend clicking the "Details" link to make your own decision on installing this package.
Deployment Method: Individual Install, Upgrade, & Uninstall
To install Vim Tux (Portable), run the following command from the command line or from PowerShell:
To upgrade Vim Tux (Portable), run the following command from the command line or from PowerShell:
To uninstall Vim Tux (Portable), run the following command from the command line or from PowerShell:
Deployment Method:
📝 NOTE: This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download vim-tux.portable --internalize --version=8.1.0297 --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade vim-tux.portable -y --source="'INTERNAL REPO URL'" --version="'8.1.0297'" [other options]
See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade vim-tux.portable -y --source="'INTERNAL REPO URL'" --version="'8.1.0297'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install vim-tux.portable
win_chocolatey:
name: vim-tux.portable
version: '8.1.0297'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'vim-tux.portable' do
action :install
source 'INTERNAL REPO URL'
version '8.1.0297'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller vim-tux.portable
{
Name = "vim-tux.portable"
Version = "8.1.0297"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'vim-tux.portable':
ensure => '8.1.0297',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.
- Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
- Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
- Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.
Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.
This package was approved as a trusted package on 20 Aug 2018.
Please visit the official site at https://tuxproject.de/projects/vim/ for more information.
Used libraries: Perl 5.24.0, Python 2.7.12, Python 3.5.2, Racket 6.6, Ruby 2.3.0, Lua 5.3.3, Tcl 8.6.4, libXpm.
Build provided by TuxProject.de - consider donating to help support their server costs.
*uganda.txt* For Vim version 8.1. Last change: 2018 May 17
VIM REFERENCE MANUAL by Bram Moolenaar
*uganda* *Uganda* *copying* *copyright* *license*
SUMMARY
*iccf* *ICCF*
Vim is Charityware. You can use and copy it as much as you like, but you are
encouraged to make a donation for needy children in Uganda. Please see |kcc|
below or visit the ICCF web site, available at these URLs:
http://iccf-holland.org/
http://www.vim.org/iccf/
http://www.iccf.nl/
You can also sponsor the development of Vim. Vim sponsors can vote for
features. See |sponsor|. The money goes to Uganda anyway.
The Open Publication License applies to the Vim documentation, see
|manual-copyright|.
=== begin of license ===
VIM LICENSE
I) There are no restrictions on distributing unmodified copies of Vim except
that they must include this license text. You can also distribute
unmodified parts of Vim, likewise unrestricted except that they must
include this license text. You are also allowed to include executables
that you made from the unmodified Vim sources, plus your own usage
examples and Vim scripts.
II) It is allowed to distribute a modified (or extended) version of Vim,
including executables and/or source code, when the following four
conditions are met:
1) This license text must be included unmodified.
2) The modified Vim must be distributed in one of the following five ways:
a) If you make changes to Vim yourself, you must clearly describe in
the distribution how to contact you. When the maintainer asks you
(in any way) for a copy of the modified Vim you distributed, you
must make your changes, including source code, available to the
maintainer without fee. The maintainer reserves the right to
include your changes in the official version of Vim. What the
maintainer will do with your changes and under what license they
will be distributed is negotiable. If there has been no negotiation
then this license, or a later version, also applies to your changes.
The current maintainer is Bram Moolenaar <[email protected]>. If this
changes it will be announced in appropriate places (most likely
vim.sf.net, www.vim.org and/or comp.editors). When it is completely
impossible to contact the maintainer, the obligation to send him
your changes ceases. Once the maintainer has confirmed that he has
received your changes they will not have to be sent again.
b) If you have received a modified Vim that was distributed as
mentioned under a) you are allowed to further distribute it
unmodified, as mentioned at I). If you make additional changes the
text under a) applies to those changes.
c) Provide all the changes, including source code, with every copy of
the modified Vim you distribute. This may be done in the form of a
context diff. You can choose what license to use for new code you
add. The changes and their license must not restrict others from
making their own changes to the official version of Vim.
d) When you have a modified Vim which includes changes as mentioned
under c), you can distribute it without the source code for the
changes if the following three conditions are met:
- The license that applies to the changes permits you to distribute
the changes to the Vim maintainer without fee or restriction, and
permits the Vim maintainer to include the changes in the official
version of Vim without fee or restriction.
- You keep the changes for at least three years after last
distributing the corresponding modified Vim. When the maintainer
or someone who you distributed the modified Vim to asks you (in
any way) for the changes within this period, you must make them
available to him.
- You clearly describe in the distribution how to contact you. This
contact information must remain valid for at least three years
after last distributing the corresponding modified Vim, or as long
as possible.
e) When the GNU General Public License (GPL) applies to the changes,
you can distribute the modified Vim under the GNU GPL version 2 or
any later version.
3) A message must be added, at least in the output of the ":version"
command and in the intro screen, such that the user of the modified Vim
is able to see that it was modified. When distributing as mentioned
under 2)e) adding the message is only required for as far as this does
not conflict with the license used for the changes.
4) The contact information as required under 2)a) and 2)d) must not be
removed or changed, except that the person himself can make
corrections.
III) If you distribute a modified version of Vim, you are encouraged to use
the Vim license for your changes and make them available to the
maintainer, including the source code. The preferred way to do this is
by e-mail or by uploading the files to a server and e-mailing the URL.
If the number of changes is small (e.g., a modified Makefile) e-mailing a
context diff will do. The e-mail address to be used is
<[email protected]>
IV) It is not allowed to remove this license from the distribution of the Vim
sources, parts of it or from a modified version. You may use this
license for previous Vim releases instead of the license that they came
with, at your option.
=== end of license ===
Note:
- If you are happy with Vim, please express that by reading the rest of this
file and consider helping needy children in Uganda.
- If you want to support further Vim development consider becoming a
|sponsor|. The money goes to Uganda anyway.
- According to Richard Stallman the Vim license is GNU GPL compatible.
A few minor changes have been made since he checked it, but that should not
make a difference.
- If you link Vim with a library that goes under the GNU GPL, this limits
further distribution to the GNU GPL. Also when you didn't actually change
anything in Vim.
- Once a change is included that goes under the GNU GPL, this forces all
further changes to also be made under the GNU GPL or a compatible license.
- If you distribute a modified version of Vim, you can include your name and
contact information with the "--with-modified-by" configure argument or the
MODIFIED_BY define.
==============================================================================
Kibaale Children's Centre *kcc* *Kibaale* *charity*
Kibaale Children's Centre (KCC) is located in Kibaale, a small town in the
south of Uganda, near Tanzania, in East Africa. The area is known as Rakai
District. The population is mostly farmers. Although people are poor, there
is enough food. But this district is suffering from AIDS more than any other
part of the world. Some say that it started there. Estimations are that 10
to 30% of the Ugandans are infected with HIV. Because parents die, there are
many orphans. In this district about 60,000 children have lost one or both
parents, out of a population of 350,000. And this is still continuing.
The children need a lot of help. The KCC is working hard to provide the needy
with food, medical care and education. Food and medical care to keep them
healthy now, and education so that they can take care of themselves in the
future. KCC works on a Christian base, but help is given to children of any
religion.
The key to solving the problems in this area is education. This has been
neglected in the past years with president Idi Amin and the following civil
wars. Now that the government is stable again, the children and parents have
to learn how to take care of themselves and how to avoid infections. There is
also help for people who are ill and hungry, but the primary goal is to
prevent people from getting ill and to teach them how to grow healthy food.
Most of the orphans are living in an extended family. An uncle or older
sister is taking care of them. Because these families are big and the income
(if any) is low, a child is lucky if it gets healthy food. Clothes, medical
care and schooling is beyond its reach. To help these needy children, a
sponsorship program was put into place. A child can be financially adopted.
For a few dollars a month KCC sees to it that the child gets indispensable
items, is healthy, goes to school and KCC takes care of anything else that
needs to be done for the child and the family that supports it.
Besides helping the child directly, the environment where the child grows up
needs to be improved. KCC helps schools to improve their teaching methods.
There is a demonstration school at the centre and teacher trainings are given.
Health workers are being trained, hygiene education is carried out and
households are stimulated to build a proper latrine. I helped setting up a
production site for cement slabs. These are used to build a good latrine.
They are sold below cost price.
There is a small clinic at the project, which provides children and their
family with medical help. When needed, transport to a hospital is offered.
Immunization programs are carried out and help is provided when an epidemic is
breaking out (measles and cholera have been a problem).
*donate*
Summer 1994 to summer 1995 I spent a whole year at the centre, working as a
volunteer. I have helped to expand the centre and worked in the area of water
and sanitation. I learned that the help that the KCC provides really helps.
When I came back to Holland, I wanted to continue supporting KCC. To do this
I'm raising funds and organizing the sponsorship program. Please consider one
of these possibilities:
1. Sponsor a child in primary school: 17 euro a month (or more).
2. Sponsor a child in secondary school: 25 euro a month (or more).
3. Sponsor the clinic: Any amount a month or quarter
4. A one-time donation
Compared with other organizations that do child sponsorship the amounts are
very low. This is because the money goes directly to the centre. Less than
5% is used for administration. This is possible because this is a small
organization that works with volunteers. If you would like to sponsor a
child, you should have the intention to do this for at least one year.
How do you know that the money will be spent right? First of all you have my
personal guarantee as the author of Vim. I trust the people that are working
at the centre, I know them personally. Furthermore, the centre has been
co-sponsored and inspected by World Vision, Save the Children Fund and is now
under the supervision of Pacific Academy Outreach Society. The centre is
visited about once a year to check the progress (at our own cost). I have
visited the centre myself many times, starting in 1993. The visit reports are
on the ICCF web site.
If you have any further questions, send me e-mail: <[email protected]>.
The address of the centre is:
Kibaale Children's Centre
p.o. box 1658
Masaka, Uganda, East Africa
Sending money: *iccf-donations*
Check the ICCF web site for the latest information! See |iccf| for the URL.
USA: The methods mentioned below can be used.
Sending a check to the Nehemiah Group Outreach Society (NGOS)
is no longer possible, unfortunately. We are looking for
another way to get you an IRS tax receipt.
For sponsoring a child contact KCF in Canada (see below). US
checks can be sent to them to lower banking costs.
Canada: Contact Kibaale Children's Fund (KCF) in Surrey, Canada. They
take care of the Canadian sponsors for the children in
Kibaale. KCF forwards 100% of the money to the project in
Uganda. You can send them a one time donation directly.
Please send me a note so that I know what has been donated
because of Vim. Ask KCF for information about sponsorship.
Kibaale Children's Fund c/o Pacific Academy
10238-168 Street
Surrey, B.C. V4N 1Z4
Canada
Phone: 604-581-5353
If you make a donation to Kibaale Children's Fund (KCF) you
will receive a tax receipt which can be submitted with your
tax return.
Holland: Transfer to the account of "Stichting ICCF Holland" in Lisse.
This will allow for tax deduction if you live in Holland.
Postbank, nr. 4548774
IBAN: NL95 INGB 0004 5487 74
Germany: It is possible to make donations that allow for a tax return.
Check the ICCF web site for the latest information:
http://iccf-holland.org/germany.html
World: Use a postal money order. That should be possible from any
country, mostly from the post office. Use this name (which is
in my passport): "Abraham Moolenaar". Use Euro for the
currency if possible.
Europe: Use a bank transfer if possible. Your bank should have a form
that you can use for this. See "Others" below for the swift
code and IBAN number.
Any other method should work. Ask for information about
sponsorship.
Credit Card: You can use PayPal to send money with a Credit card. This is
the most widely used Internet based payment system. It's
really simple to use. Use this link to find more info:
https://www.paypal.com/en_US/mrb/pal=XAC62PML3GF8Q
The e-mail address for sending the money to is:
[email protected]
For amounts above 400 Euro ($500) sending a check is
preferred.
Others: Transfer to one of these accounts if possible:
Postbank, account 4548774
Swift code: INGB NL 2A
IBAN: NL95 INGB 0004 5487 74
under the name "stichting ICCF Holland", Lisse
If that doesn't work:
Rabobank Lisse, account 3765.05.117
Swift code: RABO NL 2U
under the name "Bram Moolenaar", Lisse
Otherwise, send a check in euro or US dollars to the address
below. Minimal amount: $70 (my bank does not accept smaller
amounts for foreign check, sorry)
Address to send checks to:
Bram Moolenaar
Finsterruetihof 1
8134 Adliswil
Switzerland
This address is expected to be valid for a long time.
vim:tw=78:ts=8:ft=help:norl:
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
The embedded software have been downloaded from the listed download
location on <https://tuxproject.de/projects/vim/>
and can be verified by doing the following:
1. Download the following installers:
32-Bit: <http://tuxproject.de/projects/vim/complete-x86.7z>
64-Bit: <http://tuxproject.de/projects/vim/complete-x64.7z>
2. Get the checksum using one of the following methods:
- Using powershell function 'Get-FileHash'
- Use chocolatey utility 'checksum.exe'
3. The checksums should match the following:
checksumType: sha256
checksum32: F13600B2D3B53FD331AED55086620E55909F2FADD3D7CEBEEFFE686F58047E74
checksum64: 7728A998C3FCDFA8E0334005DC02ED3D34D7ABDECB9F186162FBE4AE195B2865
The file 'LICENSE.txt' has been obtained from <https://github.com/vim/vim/blob/master/runtime/doc/uganda.txt>
$ErrorActionPreference = 'Stop'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$destDir = Join-Path $toolsDir "vim81"
if ($Env:ChocolateyPackageParameters -match '/InstallDir:\s*(.+)') {
$destDir = $Matches[1]
$destDir = $destDir -replace '^[''"]|[''"]$' # Strip quotations. Necessary?
$destDir = $destDir -replace '[\/]$' # Remove any slashes from end of line
if (-not ($destDir.EndsWith('vim81'))) { $destDir = Join-Path $destDir 'vim81' } # Vim will not run if it is not within folder vim81
}
$packageArgs = @{
packageName = 'vim-tux.portable'
filetype = 'exe'
file = gi $toolsDir\*_x32.exe
file64 = gi $toolsDir\*_x64.exe
silentArgs = "-o`"$destDir`" -y"
}
Install-ChocolateyPackage @packageArgs
(Get-Item $destdir\patch.exe).LastWriteTime = (Get-Date) # exe must be newer than manifest; Supplied manifest fixes useless UAC request
# Rather than letting the installer place the batch files in C:\WINDOWS, I have included them in this package.
# Installing them in this way ensures the package is compatible with non-admin installs, as a good portable package should :)
Get-ChildItem "$destDir\*.bat" | %{ Install-BinFile -Name $_.BaseName -Path $_ }
Remove-Item -Force -ea 0 "$toolsDir\*_x32.exe","$toolsDir\*_x64.exe"
Write-Output 'Build provided by TuxProject.de - consider donating to help support their server costs.'
$packageName = 'vim-tux.portable'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$destDir = Join-Path $toolsDir "vim81"
Get-ChildItem "$destDir\*.bat" | %{ Uninstall-BinFile -Name $_.BaseName -Path $_ }
md5: 9F8EA4F10F07D8723C513398EDDCE494 | sha1: 1135F41E0C8CC36C3466B613ABC5A9B13F8FDE0D | sha256: 7728A998C3FCDFA8E0334005DC02ED3D34D7ABDECB9F186162FBE4AE195B2865 | sha512: FC9E3D68D49FBD6B682668D2650D23C821177DBE531FD312F04BAAF5C9ABD282F7FC36A5ABF9145D4AFFD86DBDA65C91128DD5E945666B2BF1E9B0CF4DFE766E
md5: D54982D3A90A265E29B9F50E6E33F32A | sha1: A13D5314B3F1B484D89E511C57A37C845683C69C | sha256: F13600B2D3B53FD331AED55086620E55909F2FADD3D7CEBEEFFE686F58047E74 | sha512: 82B5EF53EA34B4C67863FCF9A671E2EDBE0DBD16465DFBF616882356DBACD08F67564E49039A18E474122C61762E1BE80C17E6CA341FBDD5D18409678D2D37BB
@echo off
rem -- Run Vim --
setlocal
set VIM_EXE_DIR=%ChocolateyInstall%\lib\vim-tux.portable\tools\vim81
if exist "%VIM%\vim81\gvim.exe" set VIM_EXE_DIR=%VIM%\vim81
if exist "%VIMRUNTIME%\gvim.exe" set VIM_EXE_DIR=%VIMRUNTIME%
if exist "%VIM_EXE_DIR%\gvim.exe" goto havevim
echo "%VIM_EXE_DIR%\gvim.exe" not found
goto eof
:havevim
rem collect the arguments in VIMARGS for Win95
set VIMARGS=
set VIMNOFORK=
:loopstart
if .%1==. goto loopend
if NOT .%1==.--nofork goto noforklongarg
set VIMNOFORK=1
:noforklongarg
if NOT .%1==.-f goto noforkarg
set VIMNOFORK=1
:noforkarg
set VIMARGS=%VIMARGS% %1
shift
goto loopstart
:loopend
if .%OS%==.Windows_NT goto ntaction
if .%VIMNOFORK%==.1 goto nofork
start "%VIM_EXE_DIR%\gvim.exe" -y %VIMARGS%
goto eof
:nofork
start /w "%VIM_EXE_DIR%\gvim.exe" -y %VIMARGS%
goto eof
:ntaction
rem for WinNT we can use %*
if .%VIMNOFORK%==.1 goto noforknt
start "dummy" /b "%VIM_EXE_DIR%\gvim.exe" -y %*
goto eof
:noforknt
start "dummy" /b /wait "%VIM_EXE_DIR%\gvim.exe" -y %*
:eof
set VIMARGS=
set VIMNOFORK=
@echo off
rem -- Run Vim --
setlocal
set VIM_EXE_DIR=%ChocolateyInstall%\lib\vim-tux.portable\tools\vim81
if exist "%VIM%\vim81\gvim.exe" set VIM_EXE_DIR=%VIM%\vim81
if exist "%VIMRUNTIME%\gvim.exe" set VIM_EXE_DIR=%VIMRUNTIME%
if exist "%VIM_EXE_DIR%\gvim.exe" goto havevim
echo "%VIM_EXE_DIR%\gvim.exe" not found
goto eof
:havevim
rem collect the arguments in VIMARGS for Win95
set VIMARGS=
set VIMNOFORK=
:loopstart
if .%1==. goto loopend
if NOT .%1==.--nofork goto noforklongarg
set VIMNOFORK=1
:noforklongarg
if NOT .%1==.-f goto noforkarg
set VIMNOFORK=1
:noforkarg
set VIMARGS=%VIMARGS% %1
shift
goto loopstart
:loopend
if .%OS%==.Windows_NT goto ntaction
if .%VIMNOFORK%==.1 goto nofork
start "%VIM_EXE_DIR%\gvim.exe" -R %VIMARGS%
goto eof
:nofork
start /w "%VIM_EXE_DIR%\gvim.exe" -R %VIMARGS%
goto eof
:ntaction
rem for WinNT we can use %*
if .%VIMNOFORK%==.1 goto noforknt
start "dummy" /b "%VIM_EXE_DIR%\gvim.exe" -R %*
goto eof
:noforknt
start "dummy" /b /wait "%VIM_EXE_DIR%\gvim.exe" -R %*
:eof
set VIMARGS=
set VIMNOFORK=
@echo off
rem -- Run Vim --
setlocal
set VIM_EXE_DIR=%ChocolateyInstall%\lib\vim-tux.portable\tools\vim81
if exist "%VIM%\vim81\gvim.exe" set VIM_EXE_DIR=%VIM%\vim81
if exist "%VIMRUNTIME%\gvim.exe" set VIM_EXE_DIR=%VIMRUNTIME%
if exist "%VIM_EXE_DIR%\gvim.exe" goto havevim
echo "%VIM_EXE_DIR%\gvim.exe" not found
goto eof
:havevim
rem collect the arguments in VIMARGS for Win95
set VIMARGS=
set VIMNOFORK=
:loopstart
if .%1==. goto loopend
if NOT .%1==.--nofork goto noforklongarg
set VIMNOFORK=1
:noforklongarg
if NOT .%1==.-f goto noforkarg
set VIMNOFORK=1
:noforkarg
set VIMARGS=%VIMARGS% %1
shift
goto loopstart
:loopend
if .%OS%==.Windows_NT goto ntaction
if .%VIMNOFORK%==.1 goto nofork
start "%VIM_EXE_DIR%\gvim.exe" %VIMARGS%
goto eof
:nofork
start /w "%VIM_EXE_DIR%\gvim.exe" %VIMARGS%
goto eof
:ntaction
rem for WinNT we can use %*
if .%VIMNOFORK%==.1 goto noforknt
start "dummy" /b "%VIM_EXE_DIR%\gvim.exe" %*
goto eof
:noforknt
start "dummy" /b /wait "%VIM_EXE_DIR%\gvim.exe" %*
:eof
set VIMARGS=
set VIMNOFORK=
@echo off
rem -- Run Vim --
setlocal
set VIM_EXE_DIR=%ChocolateyInstall%\lib\vim-tux.portable\tools\vim81
if exist "%VIM%\vim81\gvim.exe" set VIM_EXE_DIR=%VIM%\vim81
if exist "%VIMRUNTIME%\gvim.exe" set VIM_EXE_DIR=%VIMRUNTIME%
if exist "%VIM_EXE_DIR%\gvim.exe" goto havevim
echo "%VIM_EXE_DIR%\gvim.exe" not found
goto eof
:havevim
rem collect the arguments in VIMARGS for Win95
set VIMARGS=
set VIMNOFORK=
:loopstart
if .%1==. goto loopend
if NOT .%1==.--nofork goto noforklongarg
set VIMNOFORK=1
:noforklongarg
if NOT .%1==.-f goto noforkarg
set VIMNOFORK=1
:noforkarg
set VIMARGS=%VIMARGS% %1
shift
goto loopstart
:loopend
if .%OS%==.Windows_NT goto ntaction
if .%VIMNOFORK%==.1 goto nofork
start "%VIM_EXE_DIR%\gvim.exe" -d %VIMARGS%
goto eof
:nofork
start /w "%VIM_EXE_DIR%\gvim.exe" -d %VIMARGS%
goto eof
:ntaction
rem for WinNT we can use %*
if .%VIMNOFORK%==.1 goto noforknt
start "dummy" /b "%VIM_EXE_DIR%\gvim.exe" -d %*
goto eof
:noforknt
start "dummy" /b /wait "%VIM_EXE_DIR%\gvim.exe" -d %*
:eof
set VIMARGS=
set VIMNOFORK=
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<!-- Make sure that UAC believes
that it does not require administrative privilege -->
<requestedExecutionLevel level="asInvoker" uiAccess="false"/>
</requestedPrivileges>
</security>
</trustInfo>
</assembly>
@echo off
rem -- Run Vim --
setlocal
set VIM_EXE_DIR=%ChocolateyInstall%\lib\vim-tux.portable\tools\vim81
if exist "%VIM%\vim81\vim.exe" set VIM_EXE_DIR=%VIM%\vim81
if exist "%VIMRUNTIME%\vim.exe" set VIM_EXE_DIR=%VIMRUNTIME%
if exist "%VIM_EXE_DIR%\vim.exe" goto havevim
echo "%VIM_EXE_DIR%\vim.exe" not found
goto eof
:havevim
rem collect the arguments in VIMARGS for Win95
set VIMARGS=
:loopstart
if .%1==. goto loopend
set VIMARGS=%VIMARGS% %1
shift
goto loopstart
:loopend
if .%OS%==.Windows_NT goto ntaction
"%VIM_EXE_DIR%\vim.exe" -R %VIMARGS%
goto eof
:ntaction
rem for WinNT we can use %*
"%VIM_EXE_DIR%\vim.exe" -R %*
goto eof
:eof
set VIMARGS=
@echo off
rem -- Run Vim --
setlocal
set VIM_EXE_DIR=%ChocolateyInstall%\lib\vim-tux.portable\tools\vim81
if exist "%VIM%\vim81\vim.exe" set VIM_EXE_DIR=%VIM%\vim81
if exist "%VIMRUNTIME%\vim.exe" set VIM_EXE_DIR=%VIMRUNTIME%
if exist "%VIM_EXE_DIR%\vim.exe" goto havevim
echo "%VIM_EXE_DIR%\vim.exe" not found
goto eof
:havevim
rem collect the arguments in VIMARGS for Win95
set VIMARGS=
:loopstart
if .%1==. goto loopend
set VIMARGS=%VIMARGS% %1
shift
goto loopstart
:loopend
if .%OS%==.Windows_NT goto ntaction
"%VIM_EXE_DIR%\vim.exe" %VIMARGS%
goto eof
:ntaction
rem for WinNT we can use %*
"%VIM_EXE_DIR%\vim.exe" %*
goto eof
:eof
set VIMARGS=
@echo off
rem -- Run Vim --
setlocal
set VIM_EXE_DIR=%ChocolateyInstall%\lib\vim-tux.portable\tools\vim81
if exist "%VIM%\vim81\vim.exe" set VIM_EXE_DIR=%VIM%\vim81
if exist "%VIMRUNTIME%\vim.exe" set VIM_EXE_DIR=%VIMRUNTIME%
if exist "%VIM_EXE_DIR%\vim.exe" goto havevim
echo "%VIM_EXE_DIR%\vim.exe" not found
goto eof
:havevim
rem collect the arguments in VIMARGS for Win95
set VIMARGS=
:loopstart
if .%1==. goto loopend
set VIMARGS=%VIMARGS% %1
shift
goto loopstart
:loopend
if .%OS%==.Windows_NT goto ntaction
"%VIM_EXE_DIR%\vim.exe" -d %VIMARGS%
goto eof
:ntaction
rem for WinNT we can use %*
"%VIM_EXE_DIR%\vim.exe" -d %*
goto eof
:eof
set VIMARGS=
Log in or click on link to see number of positives.
- VisVim.dll (f522b9acbd38) - ## / 68
- diff.exe (4ceceebc8150) - ## / 67
- patch.exe (efc277fe48ca) - ## / 67
- winpty-agent.exe (9add1a61155e) - ## / 67
- winpty.dll (936f611c2129) - ## / 66
- winpty-agent.exe (ee44e845e0a6) - ## / 66
- winpty.dll (16df8e023ce3) - ## / 59
- vim-tux.portableInstall.exe (7728a998c3fc) - ## / 68
- vim-tux.portableInstall.exe (f13600b2d3b5) - ## / 69
- vim-tux.portable.8.1.0297.nupkg (d15a7b51919f) - ## / 61
- gvim.exe (95fea49ef09d) - ## / 68
- gvimext.dll (e1f13e4fe09c) - ## / 66
- gvim_noOLE.exe (e2bde3c2f43d) - ## / 68
- install.exe (3be2f2a04eee) - ## / 68
- tee.exe (46238174aa74) - ## / 68
- uninstal.exe (91fb8c7b89b1) - ## / 68
- vim.exe (3fb500c310b2) - ## / 68
- vimrun.exe (a7df7ce93731) - ## / 67
- xxd.exe (8d6649a43817) - ## / 68
- gvim.exe (4af5951e94e3) - ## / 68
- gvimext.dll (92264c9599c1) - ## / 67
- gvim_noOLE.exe (d2772ce39238) - ## / 68
- install.exe (afbdab5b65a9) - ## / 67
- tee.exe (6c29dd6148a1) - ## / 68
- uninstal.exe (032c332efd79) - ## / 68
- vim.exe (b740573aa8cd) - ## / 69
- vimrun.exe (e0baf31ac984) - ## / 68
- xxd.exe (ab8ecd7edf17) - ## / 68
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
Vim Tux (Portable) 8.2.3908 | 130 | Monday, December 27, 2021 | Approved | |
Vim Tux (Portable) 8.2.3875 | 33 | Thursday, December 23, 2021 | Approved | |
Vim Tux (Portable) 8.2.3858 | 30 | Tuesday, December 21, 2021 | Approved | |
Vim Tux (Portable) 8.2.3836 | 25 | Saturday, December 18, 2021 | Approved | |
Vim Tux (Portable) 8.2.3811 | 25 | Wednesday, December 15, 2021 | Approved | |
Vim Tux (Portable) 8.2.3794 | 27 | Tuesday, December 14, 2021 | Approved | |
Vim Tux (Portable) 8.2.3763 | 33 | Friday, December 10, 2021 | Approved | |
Vim Tux (Portable) 8.2.3757 | 27 | Wednesday, December 8, 2021 | Approved | |
Vim Tux (Portable) 8.2.3752 | 29 | Tuesday, December 7, 2021 | Approved | |
Vim Tux (Portable) 8.2.3718 | 35 | Friday, December 3, 2021 | Approved | |
Vim Tux (Portable) 8.2.3717 | 29 | Thursday, December 2, 2021 | Approved | |
Vim Tux (Portable) 8.2.3701 | 22 | Tuesday, November 30, 2021 | Approved | |
Vim Tux (Portable) 8.2.3692 | 26 | Monday, November 29, 2021 | Approved | |
Vim Tux (Portable) 8.2.3671 | 33 | Friday, November 26, 2021 | Approved | |
Vim Tux (Portable) 8.2.3659 | 27 | Thursday, November 25, 2021 | Approved | |
Vim Tux (Portable) 8.2.3651 | 31 | Tuesday, November 23, 2021 | Approved | |
Vim Tux (Portable) 8.2.3646 | 24 | Tuesday, November 23, 2021 | Approved | |
Vim Tux (Portable) 8.2.3623 | 31 | Saturday, November 20, 2021 | Approved | |
Vim Tux (Portable) 8.2.3608 | 35 | Thursday, November 18, 2021 | Approved | |
Vim Tux (Portable) 8.2.3595 | 34 | Tuesday, November 16, 2021 | Approved | |
Vim Tux (Portable) 8.2.3579 | 44 | Friday, November 5, 2021 | Approved | |
Vim Tux (Portable) 8.2.3565 | 39 | Wednesday, October 27, 2021 | Approved | |
Vim Tux (Portable) 8.2.3551 | 26 | Friday, October 22, 2021 | Approved | |
Vim Tux (Portable) 8.2.3545 | 32 | Thursday, October 21, 2021 | Approved | |
Vim Tux (Portable) 8.2.3532 | 29 | Tuesday, October 19, 2021 | Approved | |
Vim Tux (Portable) 8.2.3513 | 41 | Saturday, October 16, 2021 | Approved | |
Vim Tux (Portable) 8.2.3505 | 36 | Thursday, October 14, 2021 | Approved | |
Vim Tux (Portable) 8.2.3493 | 33 | Tuesday, October 12, 2021 | Approved | |
Vim Tux (Portable) 8.2.3486 | 27 | Saturday, October 9, 2021 | Approved | |
Vim Tux (Portable) 8.2.3484 | 28 | Thursday, October 7, 2021 | Approved | |
Vim Tux (Portable) 8.2.3478 | 27 | Wednesday, October 6, 2021 | Approved | |
Vim Tux (Portable) 8.2.3469 | 31 | Tuesday, October 5, 2021 | Approved | |
Vim Tux (Portable) 8.2.3458 | 41 | Tuesday, September 28, 2021 | Approved | |
Vim Tux (Portable) 8.2.3455 | 32 | Thursday, September 23, 2021 | Approved | |
Vim Tux (Portable) 8.2.3450 | 33 | Tuesday, September 21, 2021 | Approved | |
Vim Tux (Portable) 8.2.3448 | 34 | Sunday, September 19, 2021 | Approved | |
Vim Tux (Portable) 8.2.3434 | 39 | Tuesday, September 14, 2021 | Approved | |
Vim Tux (Portable) 8.2.3416 | 36 | Thursday, September 9, 2021 | Approved | |
Vim Tux (Portable) 8.2.3394 | 34 | Thursday, September 2, 2021 | Approved | |
Vim Tux (Portable) 8.2.3391 | 51 | Wednesday, September 1, 2021 | Approved | |
Vim Tux (Portable) 8.2.3376 | 40 | Friday, August 27, 2021 | Approved | |
Vim Tux (Portable) 8.2.3358 | 51 | Friday, August 20, 2021 | Approved | |
Vim Tux (Portable) 8.2.3356 | 33 | Wednesday, August 18, 2021 | Approved | |
Vim Tux (Portable) 8.2.3326 | 60 | Wednesday, August 11, 2021 | Approved | |
Vim Tux (Portable) 8.2.3318 | 40 | Monday, August 9, 2021 | Approved | |
Vim Tux (Portable) 8.2.3299 | 35 | Friday, August 6, 2021 | Approved | |
Vim Tux (Portable) 8.2.3290 | 26 | Thursday, August 5, 2021 | Approved | |
Vim Tux (Portable) 8.2.3281 | 42 | Wednesday, August 4, 2021 | Approved | |
Vim Tux (Portable) 8.2.3273 | 34 | Tuesday, August 3, 2021 | Approved | |
Vim Tux (Portable) 8.2.3269 | 33 | Monday, August 2, 2021 | Approved | |
Vim Tux (Portable) 8.2.3263 | 28 | Sunday, August 1, 2021 | Approved | |
Vim Tux (Portable) 8.2.3253 | 57 | Saturday, July 31, 2021 | Approved | |
Vim Tux (Portable) 8.2.3242 | 32 | Thursday, July 29, 2021 | Approved | |
Vim Tux (Portable) 8.2.3223 | 35 | Tuesday, July 27, 2021 | Approved | |
Vim Tux (Portable) 8.2.3204 | 37 | Friday, July 23, 2021 | Approved | |
Vim Tux (Portable) 8.2.3187 | 36 | Tuesday, July 20, 2021 | Approved | |
Vim Tux (Portable) 8.2.3171 | 45 | Friday, July 16, 2021 | Approved | |
Vim Tux (Portable) 8.2.3158 | 66 | Wednesday, July 14, 2021 | Approved | |
Vim Tux (Portable) 8.2.3131 | 39 | Friday, July 9, 2021 | Approved | |
Vim Tux (Portable) 8.2.3120 | 38 | Thursday, July 8, 2021 | Approved | |
Vim Tux (Portable) 8.2.3113 | 46 | Wednesday, July 7, 2021 | Approved | |
Vim Tux (Portable) 8.2.3107 | 38 | Tuesday, July 6, 2021 | Approved | |
Vim Tux (Portable) 8.2.3104 | 40 | Monday, July 5, 2021 | Approved | |
Vim Tux (Portable) 8.2.3095 | 36 | Sunday, July 4, 2021 | Approved | |
Vim Tux (Portable) 8.2.3080 | 43 | Thursday, July 1, 2021 | Approved | |
Vim Tux (Portable) 8.2.3075 | 35 | Wednesday, June 30, 2021 | Approved | |
Vim Tux (Portable) 8.2.3066 | 48 | Monday, June 28, 2021 | Approved | |
Vim Tux (Portable) 8.2.3055 | 39 | Sunday, June 27, 2021 | Approved | |
Vim Tux (Portable) 8.2.3043 | 35 | Thursday, June 24, 2021 | Approved | |
Vim Tux (Portable) 8.2.3033 | 39 | Tuesday, June 22, 2021 | Approved | |
Vim Tux (Portable) 8.2.3020 | 30 | Sunday, June 20, 2021 | Approved | |
Vim Tux (Portable) 8.2.3017 | 43 | Friday, June 18, 2021 | Approved | |
Vim Tux (Portable) 8.2.2840 | 93 | Saturday, May 8, 2021 | Approved | |
Vim Tux (Portable) 8.2.2832 | 46 | Wednesday, May 5, 2021 | Approved | |
Vim Tux (Portable) 8.2.2815 | 59 | Wednesday, April 28, 2021 | Approved | |
Vim Tux (Portable) 8.2.2799 | 63 | Thursday, April 22, 2021 | Approved | |
Vim Tux (Portable) 8.2.2794 | 35 | Wednesday, April 21, 2021 | Approved | |
Vim Tux (Portable) 8.2.2763 | 50 | Thursday, April 15, 2021 | Approved | |
Vim Tux (Portable) 8.2.2738 | 59 | Friday, April 9, 2021 | Approved | |
Vim Tux (Portable) 8.2.2730 | 45 | Wednesday, April 7, 2021 | Approved | |
Vim Tux (Portable) 8.2.2679 | 51 | Wednesday, March 31, 2021 | Approved | |
Vim Tux (Portable) 8.2.2650 | 48 | Friday, March 26, 2021 | Approved | |
Vim Tux (Portable) 8.2.2648 | 60 | Wednesday, March 24, 2021 | Approved | |
Vim Tux (Portable) 8.2.2637 | 46 | Tuesday, March 23, 2021 | Approved | |
Vim Tux (Portable) 8.2.2491 | 114 | Thursday, February 11, 2021 | Approved | |
Vim Tux (Portable) 8.2.2129 | 107 | Saturday, December 12, 2020 | Approved | |
Vim Tux (Portable) 8.2.1981 | 73 | Saturday, November 14, 2020 | Approved | |
Vim Tux (Portable) 8.2.1955 | 78 | Friday, November 6, 2020 | Approved | |
Vim Tux (Portable) 8.2.1923 | 83 | Friday, October 30, 2020 | Approved | |
Vim Tux (Portable) 8.2.1883 | 74 | Thursday, October 22, 2020 | Approved | |
Vim Tux (Portable) 8.2.1858 | 73 | Sunday, October 18, 2020 | Approved | |
Vim Tux (Portable) 8.2.1738 | 102 | Friday, September 25, 2020 | Approved | |
Vim Tux (Portable) 8.2.1651 | 89 | Thursday, September 10, 2020 | Approved | |
Vim Tux (Portable) 8.2.1058 | 173 | Friday, June 26, 2020 | Approved | |
Vim Tux (Portable) 8.2.1007 | 92 | Friday, June 19, 2020 | Approved | |
Vim Tux (Portable) 8.2.988 | 122 | Wednesday, June 17, 2020 | Approved | |
Vim Tux (Portable) 8.2.960 | 100 | Friday, June 12, 2020 | Approved | |
Vim Tux (Portable) 8.2.950 | 83 | Thursday, June 11, 2020 | Approved | |
Vim Tux (Portable) 8.2.916 | 101 | Sunday, June 7, 2020 | Approved | |
Vim Tux (Portable) 8.2.882 | 93 | Tuesday, June 2, 2020 | Approved | |
Vim Tux (Portable) 8.2.855 | 88 | Sunday, May 31, 2020 | Approved | |
Vim Tux (Portable) 8.2.834 | 102 | Friday, May 29, 2020 | Approved | |
Vim Tux (Portable) 8.2.829 | 114 | Wednesday, May 27, 2020 | Approved | |
Vim Tux (Portable) 8.2.821 | 77 | Tuesday, May 26, 2020 | Approved | |
Vim Tux (Portable) 8.2.806 | 100 | Friday, May 22, 2020 | Approved | |
Vim Tux (Portable) 8.2.803 | 64 | Thursday, May 21, 2020 | Approved | |
Vim Tux (Portable) 8.2.766 | 124 | Sunday, May 17, 2020 | Approved | |
Vim Tux (Portable) 8.2.750 | 95 | Thursday, May 14, 2020 | Approved | |
Vim Tux (Portable) 8.2.735 | 100 | Tuesday, May 12, 2020 | Approved | |
Vim Tux (Portable) 8.2.647 | 152 | Monday, April 27, 2020 | Approved | |
Vim Tux (Portable) 8.2.640 | 91 | Sunday, April 26, 2020 | Approved | |
Vim Tux (Portable) 8.2.625 | 94 | Friday, April 24, 2020 | Approved | |
Vim Tux (Portable) 8.2.612 | 157 | Tuesday, April 21, 2020 | Approved | |
Vim Tux (Portable) 8.2.592 | 113 | Saturday, April 18, 2020 | Approved | |
Vim Tux (Portable) 8.2.585 | 99 | Friday, April 17, 2020 | Approved | |
Vim Tux (Portable) 8.2.577 | 123 | Tuesday, April 14, 2020 | Approved | |
Vim Tux (Portable) 8.2.0536 | 109 | Sunday, April 12, 2020 | Approved | |
Vim Tux (Portable) 8.2.0515 | 103 | Monday, April 6, 2020 | Approved | |
Vim Tux (Portable) 8.2.0505 | 114 | Saturday, April 4, 2020 | Approved | |
Vim Tux (Portable) 8.2.0486 | 95 | Wednesday, April 1, 2020 | Approved | |
Vim Tux (Portable) 8.2.0464 | 114 | Sunday, March 29, 2020 | Approved | |
Vim Tux (Portable) 8.2.0397 | 122 | Wednesday, March 18, 2020 | Approved | |
Vim Tux (Portable) 8.2.0369 | 121 | Wednesday, March 11, 2020 | Approved | |
Vim Tux (Portable) 8.2.0357 | 116 | Friday, March 6, 2020 | Approved | |
Vim Tux (Portable) 8.2.0324 | 150 | Friday, February 28, 2020 | Approved | |
Vim Tux (Portable) 8.2.0313 | 110 | Monday, February 24, 2020 | Approved | |
Vim Tux (Portable) 8.2.0294 | 101 | Saturday, February 22, 2020 | Approved | |
Vim Tux (Portable) 8.2.0285 | 100 | Friday, February 21, 2020 | Approved | |
Vim Tux (Portable) 8.2.0273 | 111 | Tuesday, February 18, 2020 | Approved | |
Vim Tux (Portable) 8.2.0231 | 134 | Sunday, February 9, 2020 | Approved | |
Vim Tux (Portable) 8.2.0164 | 123 | Wednesday, January 29, 2020 | Approved | |
Vim Tux (Portable) 8.2.0147 | 86 | Saturday, January 25, 2020 | Approved | |
Vim Tux (Portable) 8.2.0129 | 147 | Sunday, January 19, 2020 | Approved | |
Vim Tux (Portable) 8.2.0114 | 114 | Tuesday, January 14, 2020 | Approved | |
Vim Tux (Portable) 8.2.0109 | 109 | Friday, January 10, 2020 | Approved | |
Vim Tux (Portable) 8.2.0092 | 122 | Tuesday, January 7, 2020 | Approved | |
Vim Tux (Portable) 8.2.0080 | 128 | Friday, January 3, 2020 | Approved | |
Vim Tux (Portable) 8.2.0065 | 110 | Tuesday, December 31, 2019 | Approved | |
Vim Tux (Portable) 8.2.0055 | 84 | Monday, December 30, 2019 | Approved | |
Vim Tux (Portable) 8.2.0052 | 91 | Sunday, December 29, 2019 | Approved | |
Vim Tux (Portable) 8.2.0033 | 103 | Tuesday, December 24, 2019 | Approved | |
Vim Tux (Portable) 8.2.0021 | 105 | Thursday, December 19, 2019 | Approved | |
Vim Tux (Portable) 8.2.0011 | 128 | Monday, December 16, 2019 | Approved | |
Vim Tux (Portable) 8.1.2333 | 156 | Friday, November 22, 2019 | Approved | |
Vim Tux (Portable) 8.1.2323 | 127 | Thursday, November 21, 2019 | Approved | |
Vim Tux (Portable) 8.1.2311 | 134 | Sunday, November 17, 2019 | Approved | |
Vim Tux (Portable) 8.1.2300 | 122 | Thursday, November 14, 2019 | Approved | |
Vim Tux (Portable) 8.1.2237 | 152 | Friday, November 1, 2019 | Approved | |
Vim Tux (Portable) 8.1.2204 | 171 | Thursday, October 24, 2019 | Approved | |
Vim Tux (Portable) 8.1.2200 | 128 | Wednesday, October 23, 2019 | Approved | |
Vim Tux (Portable) 8.1.2148 | 132 | Monday, October 14, 2019 | Approved | |
Vim Tux (Portable) 8.1.2133 | 116 | Friday, October 11, 2019 | Approved | |
Vim Tux (Portable) 8.1.2117 | 130 | Sunday, October 6, 2019 | Approved | |
Vim Tux (Portable) 8.1.2108 | 124 | Thursday, October 3, 2019 | Approved | |
Vim Tux (Portable) 8.1.2103 | 102 | Tuesday, October 1, 2019 | Approved | |
Vim Tux (Portable) 8.1.2079 | 148 | Friday, September 27, 2019 | Approved | |
Vim Tux (Portable) 8.1.2071 | 105 | Wednesday, September 25, 2019 | Approved | |
Vim Tux (Portable) 8.1.2052 | 118 | Thursday, September 19, 2019 | Approved | |
Vim Tux (Portable) 8.1.2019 | 156 | Tuesday, September 10, 2019 | Approved | |
Vim Tux (Portable) 8.1.2004 | 124 | Sunday, September 8, 2019 | Approved | |
Vim Tux (Portable) 8.1.1995 | 100 | Saturday, September 7, 2019 | Approved | |
Vim Tux (Portable) 8.1.1986 | 124 | Thursday, September 5, 2019 | Approved | |
Vim Tux (Portable) 8.1.1961 | 123 | Monday, September 2, 2019 | Approved | |
Vim Tux (Portable) 8.1.1927 | 150 | Monday, August 26, 2019 | Approved | |
Vim Tux (Portable) 8.1.1915 | 113 | Saturday, August 24, 2019 | Approved | |
Vim Tux (Portable) 8.1.1906 | 132 | Thursday, August 22, 2019 | Approved | |
Vim Tux (Portable) 8.1.1890 | 112 | Tuesday, August 20, 2019 | Approved | |
Vim Tux (Portable) 8.1.1836 | 163 | Sunday, August 11, 2019 | Approved | |
Vim Tux (Portable) 8.1.1813 | 149 | Monday, August 5, 2019 | Approved | |
Vim Tux (Portable) 8.1.1744 | 144 | Thursday, July 25, 2019 | Approved | |
Vim Tux (Portable) 8.1.1729 | 143 | Tuesday, July 23, 2019 | Approved | |
Vim Tux (Portable) 8.1.1713 | 139 | Friday, July 19, 2019 | Approved | |
Vim Tux (Portable) 8.1.1695 | 123 | Tuesday, July 16, 2019 | Approved | |
Vim Tux (Portable) 8.1.1669 | 109 | Saturday, July 13, 2019 | Approved | |
Vim Tux (Portable) 8.1.1655 | 156 | Tuesday, July 9, 2019 | Approved | |
Vim Tux (Portable) 8.1.1631 | 119 | Friday, July 5, 2019 | Approved | |
Vim Tux (Portable) 8.1.1601 | 155 | Thursday, June 27, 2019 | Approved | |
Vim Tux (Portable) 8.1.1578 | 142 | Saturday, June 22, 2019 | Approved | |
Vim Tux (Portable) 8.1.1573 | 139 | Thursday, June 20, 2019 | Approved | |
Vim Tux (Portable) 8.1.1566 | 124 | Tuesday, June 18, 2019 | Approved | |
Vim Tux (Portable) 8.1.1557 | 116 | Monday, June 17, 2019 | Approved | |
Vim Tux (Portable) 8.1.1536 | 107 | Sunday, June 16, 2019 | Approved | |
Vim Tux (Portable) 8.1.1523 | 134 | Friday, June 14, 2019 | Approved | |
Vim Tux (Portable) 8.1.1515 | 162 | Tuesday, June 11, 2019 | Approved | |
Vim Tux (Portable) 8.1.1511 | 142 | Monday, June 10, 2019 | Approved | |
Vim Tux (Portable) 8.1.1455 | 140 | Monday, June 3, 2019 | Approved | |
Vim Tux (Portable) 8.1.1432 | 151 | Friday, May 31, 2019 | Approved | |
Vim Tux (Portable) 8.1.1413 | 155 | Tuesday, May 28, 2019 | Approved | |
Vim Tux (Portable) 8.1.1373 | 156 | Friday, May 24, 2019 | Approved | |
Vim Tux (Portable) 8.1.1364 | 139 | Thursday, May 23, 2019 | Approved | |
Vim Tux (Portable) 8.1.1353 | 125 | Monday, May 20, 2019 | Approved | |
Vim Tux (Portable) 8.1.1333 | 140 | Thursday, May 16, 2019 | Approved | |
Vim Tux (Portable) 8.1.1328 | 140 | Monday, May 13, 2019 | Approved | |
Vim Tux (Portable) 8.1.1312 | 114 | Saturday, May 11, 2019 | Approved | |
Vim Tux (Portable) 8.1.1298 | 153 | Thursday, May 9, 2019 | Approved | |
Vim Tux (Portable) 8.1.1286 | 156 | Tuesday, May 7, 2019 | Approved | |
Vim Tux (Portable) 8.1.1197 | 153 | Monday, April 22, 2019 | Approved | |
Vim Tux (Portable) 8.1.1183 | 142 | Thursday, April 18, 2019 | Approved | |
Vim Tux (Portable) 8.1.1165 | 142 | Sunday, April 14, 2019 | Approved | |
Vim Tux (Portable) 8.1.1140 | 150 | Tuesday, April 9, 2019 | Approved | |
Vim Tux (Portable) 8.1.1136 | 129 | Monday, April 8, 2019 | Approved | |
Vim Tux (Portable) 8.1.1124 | 122 | Sunday, April 7, 2019 | Approved | |
Vim Tux (Portable) 8.1.1103 | 158 | Thursday, April 4, 2019 | Approved | |
Vim Tux (Portable) 8.1.1097 | 147 | Monday, April 1, 2019 | Approved | |
Vim Tux (Portable) 8.1.1073 | 117 | Saturday, March 30, 2019 | Approved | |
Vim Tux (Portable) 8.1.1057 | 151 | Thursday, March 28, 2019 | Approved | |
Vim Tux (Portable) 8.1.1032 | 174 | Friday, March 22, 2019 | Approved | |
Vim Tux (Portable) 8.1.1027 | 150 | Thursday, March 21, 2019 | Approved | |
Vim Tux (Portable) 8.1.1017 | 107 | Tuesday, March 19, 2019 | Approved | |
Vim Tux (Portable) 8.1.1004 | 143 | Monday, March 11, 2019 | Approved | |
Vim Tux (Portable) 8.1.998 | 129 | Friday, March 8, 2019 | Approved | |
Vim Tux (Portable) 8.1.990 | 141 | Sunday, March 3, 2019 | Approved | |
Vim Tux (Portable) 8.1.984 | 124 | Thursday, February 28, 2019 | Approved | |
Vim Tux (Portable) 8.1.978 | 135 | Saturday, February 23, 2019 | Approved | |
Vim Tux (Portable) 8.1.966 | 143 | Friday, February 22, 2019 | Approved | |
Vim Tux (Portable) 8.1.947 | 131 | Tuesday, February 19, 2019 | Approved | |
Vim Tux (Portable) 8.1.934 | 102 | Sunday, February 17, 2019 | Approved | |
Vim Tux (Portable) 8.1.926 | 124 | Saturday, February 16, 2019 | Approved | |
Vim Tux (Portable) 8.1.909 | 114 | Thursday, February 14, 2019 | Approved | |
Vim Tux (Portable) 8.1.895 | 139 | Tuesday, February 12, 2019 | Approved | |
Vim Tux (Portable) 8.1.0885 | 142 | Sunday, February 10, 2019 | Approved | |
Vim Tux (Portable) 8.1.0877 | 146 | Thursday, February 7, 2019 | Approved | |
Vim Tux (Portable) 8.1.0871 | 164 | Monday, February 4, 2019 | Approved | |
Vim Tux (Portable) 8.1.0868 | 147 | Sunday, February 3, 2019 | Approved | |
Vim Tux (Portable) 8.1.0865 | 129 | Saturday, February 2, 2019 | Approved | |
Vim Tux (Portable) 8.1.0842 | 141 | Thursday, January 31, 2019 | Approved | |
Vim Tux (Portable) 8.1.0837 | 165 | Monday, January 28, 2019 | Approved | |
Vim Tux (Portable) 8.1.0814 | 144 | Friday, January 25, 2019 | Approved | |
Vim Tux (Portable) 8.1.0796 | 125 | Thursday, January 24, 2019 | Approved | |
Vim Tux (Portable) 8.1.0788 | 138 | Tuesday, January 22, 2019 | Approved | |
Vim Tux (Portable) 8.1.0757 | 165 | Thursday, January 17, 2019 | Approved | |
Vim Tux (Portable) 8.1.0749 | 121 | Tuesday, January 15, 2019 | Approved | |
Vim Tux (Portable) 8.1.0727 | 122 | Saturday, January 12, 2019 | Approved | |
Vim Tux (Portable) 8.1.0712 | 176 | Thursday, January 10, 2019 | Approved | |
Vim Tux (Portable) 8.1.0700 | 139 | Tuesday, January 8, 2019 | Approved | |
Vim Tux (Portable) 8.1.0690 | 186 | Saturday, January 5, 2019 | Approved | |
Vim Tux (Portable) 8.1.0681 | 165 | Thursday, January 3, 2019 | Approved | |
Vim Tux (Portable) 8.1.0674 | 142 | Wednesday, January 2, 2019 | Approved | |
Vim Tux (Portable) 8.1.0647 | 177 | Friday, December 28, 2018 | Approved | |
Vim Tux (Portable) 8.1.0644 | 143 | Thursday, December 27, 2018 | Approved | |
Vim Tux (Portable) 8.1.0635 | 118 | Wednesday, December 26, 2018 | Approved | |
Vim Tux (Portable) 8.1.0630 | 154 | Tuesday, December 25, 2018 | Approved | |
Vim Tux (Portable) 8.1.0629 | 135 | Monday, December 24, 2018 | Approved | |
Vim Tux (Portable) 8.1.0622 | 127 | Sunday, December 23, 2018 | Approved | |
Vim Tux (Portable) 8.1.0617 | 150 | Saturday, December 22, 2018 | Approved | |
Vim Tux (Portable) 8.1.0594 | 139 | Sunday, December 16, 2018 | Approved | |
Vim Tux (Portable) 8.1.0577 | 166 | Thursday, December 13, 2018 | Approved | |
Vim Tux (Portable) 8.1.0551 | 172 | Friday, November 30, 2018 | Approved | |
Vim Tux (Portable) 8.1.0547 | 154 | Monday, November 26, 2018 | Approved | |
Vim Tux (Portable) 8.1.0536 | 149 | Tuesday, November 20, 2018 | Approved | |
Vim Tux (Portable) 8.1.0524 | 162 | Tuesday, November 13, 2018 | Approved | |
Vim Tux (Portable) 8.1.0513 | 171 | Thursday, November 8, 2018 | Approved | |
Vim Tux (Portable) 8.1.0509 | 159 | Sunday, November 4, 2018 | Approved | |
Vim Tux (Portable) 8.1.0498 | 150 | Sunday, October 28, 2018 | Approved | |
Vim Tux (Portable) 8.1.0489 | 156 | Monday, October 22, 2018 | Approved | |
Vim Tux (Portable) 8.1.0474 | 177 | Monday, October 15, 2018 | Approved | |
Vim Tux (Portable) 8.1.0470 | 169 | Friday, October 12, 2018 | Approved | |
Vim Tux (Portable) 8.1.0451 | 196 | Friday, October 5, 2018 | Approved | |
Vim Tux (Portable) 8.1.0442 | 168 | Monday, October 1, 2018 | Approved | |
Vim Tux (Portable) 8.1.0436 | 147 | Thursday, September 27, 2018 | Approved | |
Vim Tux (Portable) 8.1.0425 | 158 | Saturday, September 22, 2018 | Approved | |
Vim Tux (Portable) 8.1.0408 | 154 | Thursday, September 20, 2018 | Approved | |
Vim Tux (Portable) 8.1.0401 | 149 | Tuesday, September 18, 2018 | Approved | |
Vim Tux (Portable) 8.1.0385 | 190 | Friday, September 14, 2018 | Approved | |
Vim Tux (Portable) 8.1.0371 | 164 | Thursday, September 13, 2018 | Approved | |
Vim Tux (Portable) 8.1.0362 | 147 | Tuesday, September 11, 2018 | Approved | |
Vim Tux (Portable) 8.1.0354 | 160 | Sunday, September 9, 2018 | Approved | |
Vim Tux (Portable) 8.1.0347 | 166 | Thursday, September 6, 2018 | Approved | |
Vim Tux (Portable) 8.1.0342 | 158 | Sunday, September 2, 2018 | Approved | |
Vim Tux (Portable) 8.1.0332 | 149 | Thursday, August 30, 2018 | Approved | |
Vim Tux (Portable) 8.1.0327 | 146 | Sunday, August 26, 2018 | Approved | |
Vim Tux (Portable) 8.1.0318 | 140 | Thursday, August 23, 2018 | Approved | |
Vim Tux (Portable) 8.1.0301 | 155 | Tuesday, August 21, 2018 | Approved | |
Vim Tux (Portable) 8.1.0297 | 168 | Monday, August 20, 2018 | Approved | |
Vim Tux (Portable) 8.1.0288 | 191 | Thursday, August 16, 2018 | Approved | |
Vim Tux (Portable) 8.1.0278 | 176 | Monday, August 13, 2018 | Approved | |
Vim Tux (Portable) 8.1.0271 | 158 | Sunday, August 12, 2018 | Approved | |
Vim Tux (Portable) 8.1.0259 | 182 | Friday, August 10, 2018 | Approved | |
Vim Tux (Portable) 8.1.0239 | 179 | Sunday, August 5, 2018 | Approved | |
Vim Tux (Portable) 8.1.0229 | 173 | Tuesday, July 31, 2018 | Approved | |
Vim Tux (Portable) 8.1.0221 | 178 | Sunday, July 29, 2018 | Approved | |
Vim Tux (Portable) 8.1.0210 | 165 | Thursday, July 26, 2018 | Approved | |
Vim Tux (Portable) 8.1.0207 | 159 | Tuesday, July 24, 2018 | Approved | |
Vim Tux (Portable) 8.1.0203 | 176 | Monday, July 23, 2018 | Approved | |
Vim Tux (Portable) 8.1.0199 | 164 | Saturday, July 21, 2018 | Approved | |
Vim Tux (Portable) 8.1.0196 | 194 | Friday, July 20, 2018 | Approved | |
Vim Tux (Portable) 8.1.0191 | 144 | Tuesday, July 17, 2018 | Approved | |
Vim Tux (Portable) 8.1.0186 | 185 | Sunday, July 15, 2018 | Approved | |
Vim Tux (Portable) 8.1.0173 | 220 | Tuesday, July 10, 2018 | Approved | |
Vim Tux (Portable) 8.1.0153 | 198 | Friday, July 6, 2018 | Approved | |
Vim Tux (Portable) 8.1.0138 | 202 | Tuesday, July 3, 2018 | Approved | |
Vim Tux (Portable) 8.1.0133 | 162 | Sunday, July 1, 2018 | Approved | |
Vim Tux (Portable) 8.1.0126 | 180 | Friday, June 29, 2018 | Approved | |
Vim Tux (Portable) 8.1.0105 | 180 | Sunday, June 24, 2018 | Approved | |
Vim Tux (Portable) 8.1.0054 | 211 | Thursday, June 14, 2018 | Approved | |
Vim Tux (Portable) 8.1.0034 | 211 | Tuesday, June 5, 2018 | Approved | |
Vim Tux (Portable) 8.1.0022 | 208 | Friday, May 25, 2018 | Approved | |
Vim Tux (Portable) 8.1.0013 | 237 | Tuesday, May 22, 2018 | Approved | |
Vim Tux (Portable) 8.1.0009 | 198 | Monday, May 21, 2018 | Approved | |
Vim Tux (Portable) 8.1.0004 | 181 | Sunday, May 20, 2018 | Approved | |
Vim Tux (Portable) 8.1.0.20180519 | 218 | Saturday, May 19, 2018 | Approved | |
Vim Tux (Portable) 8.1.0000 | 209 | Friday, May 18, 2018 | Approved | |
Vim Tux (Portable) 8.0.1848 | 250 | Thursday, May 17, 2018 | Approved | |
Vim Tux (Portable) 8.0.1831 | 217 | Monday, May 14, 2018 | Approved | |
Vim Tux (Portable) 8.0.1820 | 206 | Sunday, May 13, 2018 | Approved | |
Vim Tux (Portable) 8.0.1806 | 229 | Thursday, May 10, 2018 | Approved | |
Vim Tux (Portable) 8.0.1799 | 185 | Monday, May 7, 2018 | Approved | |
Vim Tux (Portable) 8.0.1794 | 189 | Sunday, May 6, 2018 | Approved | |
Vim Tux (Portable) 8.0.1790 | 232 | Friday, May 4, 2018 | Approved | |
Vim Tux (Portable) 8.0.1788 | 220 | Thursday, May 3, 2018 | Approved | |
Vim Tux (Portable) 8.0.1774 | 269 | Monday, April 30, 2018 | Approved | |
Vim Tux (Portable) 8.0.1765 | 212 | Thursday, April 26, 2018 | Approved | |
Vim Tux (Portable) 8.0.1748 | 202 | Sunday, April 22, 2018 | Approved | |
Vim Tux (Portable) 8.0.1736 | 222 | Friday, April 20, 2018 | Approved | |
Vim Tux (Portable) 8.0.1727 | 213 | Wednesday, April 18, 2018 | Approved | |
Vim Tux (Portable) 8.0.1705 | 206 | Saturday, April 14, 2018 | Approved | |
Vim Tux (Portable) 8.0.1679 | 216 | Monday, April 9, 2018 | Approved | |
Vim Tux (Portable) 8.0.1664 | 214 | Saturday, April 7, 2018 | Approved | |
Vim Tux (Portable) 8.0.1655 | 224 | Saturday, March 31, 2018 | Approved | |
Vim Tux (Portable) 8.0.1638 | 262 | Sunday, March 25, 2018 | Approved | |
Vim Tux (Portable) 8.0.1626 | 317 | Thursday, March 22, 2018 | Approved | |
Vim Tux (Portable) 8.0.1612 | 246 | Saturday, March 17, 2018 | Approved | |
Vim Tux (Portable) 8.0.1601 | 237 | Tuesday, March 13, 2018 | Approved | |
Vim Tux (Portable) 8.0.1591 | 264 | Friday, March 9, 2018 | Approved | |
Vim Tux (Portable) 8.0.1563 | 235 | Sunday, March 4, 2018 | Approved | |
Vim Tux (Portable) 8.0.1553 | 260 | Friday, March 2, 2018 | Approved | |
Vim Tux (Portable) 8.0.1532 | 259 | Sunday, February 25, 2018 | Approved | |
Vim Tux (Portable) 8.0.1504 | 269 | Thursday, February 15, 2018 | Approved | |
Vim Tux (Portable) 8.0.1473 | 250 | Thursday, February 8, 2018 | Approved | |
Vim Tux (Portable) 8.0.1451 | 269 | Saturday, February 3, 2018 | Approved | |
Vim Tux (Portable) 8.0.1438 | 255 | Tuesday, January 30, 2018 | Approved | |
Vim Tux (Portable) 8.0.1431 | 260 | Saturday, January 27, 2018 | Approved | |
Vim Tux (Portable) 8.0.1428 | 315 | Thursday, January 4, 2018 | Approved | |
Vim Tux (Portable) 8.0.1422 | 281 | Saturday, December 30, 2017 | Approved | |
Vim Tux (Portable) 8.0.1390 | 280 | Sunday, December 17, 2017 | Approved | |
Vim Tux (Portable) 8.0.1379 | 252 | Thursday, December 14, 2017 | Approved | |
Vim Tux (Portable) 8.0.1376 | 312 | Thursday, December 7, 2017 | Approved | |
Vim Tux (Portable) 8.0.1358 | 279 | Friday, December 1, 2017 | Approved | |
Vim Tux (Portable) 8.0.1330 | 292 | Thursday, November 23, 2017 | Approved | |
Vim Tux (Portable) 8.0.1311 | 262 | Monday, November 20, 2017 | Approved | |
Vim Tux (Portable) 8.0.1305 | 235 | Saturday, November 18, 2017 | Approved | |
Vim Tux (Portable) 8.0.1272 | 348 | Thursday, November 9, 2017 | Approved | |
Vim Tux (Portable) 8.0.1257 | 262 | Sunday, November 5, 2017 | Approved | |
Vim Tux (Portable) 8.0.1203 | 329 | Wednesday, October 18, 2017 | Approved | |
Vim Tux (Portable) 8.0.1157 | 332 | Friday, September 29, 2017 | Approved | |
Vim Tux (Portable) 8.0.1088 | 300 | Monday, September 11, 2017 | Approved | |
Vim Tux (Portable) 8.0.1010 | 313 | Tuesday, August 29, 2017 | Approved | |
Vim Tux (Portable) 8.0.0987 | 283 | Wednesday, August 23, 2017 | Approved | |
Vim Tux (Portable) 8.0.0737 | 355 | Thursday, July 20, 2017 | Approved | |
Vim Tux (Portable) 8.0.0642 | 318 | Sunday, June 18, 2017 | Approved | |
Vim Tux (Portable) 8.0.0584 | 345 | Wednesday, April 26, 2017 | Approved | |
Vim Tux (Portable) 8.0.0566 | 260 | Friday, April 21, 2017 | Approved | |
Vim Tux (Portable) 8.0.0123 | 539 | Friday, December 9, 2016 | Approved | |
Vim Tux (Portable) 8.0.0117 | 376 | Friday, December 2, 2016 | Approved | |
Vim Tux (Portable) 8.0.0066 | 344 | Thursday, November 10, 2016 | Approved | |
Vim Tux (Portable) 8.0.0051 | 374 | Friday, October 28, 2016 | Approved | |
Vim Tux (Portable) 8.0.0045 | 388 | Friday, October 21, 2016 | Approved | |
Vim Tux (Portable) 8.0.0017 | 295 | Wednesday, September 28, 2016 | Approved | |
Vim Tux (Portable) 8.0.005 | 378 | Friday, September 16, 2016 | Approved | |
Vim Tux (Portable) 7.4.2222 | 377 | Thursday, August 18, 2016 | Approved | |
Vim Tux (Portable) 7.4.2180 | 341 | Tuesday, August 9, 2016 | Approved | |
Vim Tux (Portable) 7.4.2153 | 336 | Friday, August 5, 2016 | Approved | |
Vim Tux (Portable) 7.4.2089 | 350 | Friday, July 22, 2016 | Approved | |
Vim Tux (Portable) 7.4.2034 | 337 | Friday, July 15, 2016 | Approved | |
Vim Tux (Portable) 7.4.1987 | 346 | Sunday, July 3, 2016 | Approved | |
Vim Tux (Portable) 7.4.1949 | 337 | Thursday, June 23, 2016 | Approved | |
Vim Tux (Portable) 7.4.1913 | 349 | Friday, June 10, 2016 | Approved | |
Vim Tux (Portable) 7.4.1905 | 295 | Thursday, June 9, 2016 | Approved | |
Vim Tux (Portable) 7.4.1901 | 335 | Tuesday, June 7, 2016 | Approved | |
Vim Tux (Portable) 7.4.1862 | 269 | Thursday, June 2, 2016 | Approved | |
Vim Tux (Portable) 7.4.1856 | 316 | Monday, May 30, 2016 | Approved | |
Vim Tux (Portable) 7.4.1848 | 327 | Friday, May 27, 2016 | Approved | |
Vim Tux (Portable) 7.4.1842 | 306 | Thursday, May 26, 2016 | Approved | |
Vim Tux (Portable) 7.4.1832 | 290 | Thursday, May 19, 2016 | Approved | |
Vim Tux (Portable) 7.4.1829 | 382 | Thursday, May 12, 2016 | Approved | |
Vim Tux (Portable) 7.4.1824 | 356 | Monday, May 9, 2016 | Approved |
Ground Rules:
- This discussion is only about Vim Tux (Portable) and the Vim Tux (Portable) package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or Vim Tux (Portable), or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.