Step 1: Review Your Packages

Step 2: Choose Your Integration Method

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

Option 2: Internalized Package (Reliable, Scalable)

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

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:

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 ###

#### 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.2.4.3.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.2.4.3.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.2.4.3.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.2.4.3.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

Downloads:

122,386

Downloads of v 8.0.005:

503

Last Update:

16 Sep 2016

Package Maintainer(s):

Pauby

Software Author(s):

Build: TuxProject.de
Developer: vim team

Tags:

Vim Tux (Portable)

This is not the latest version of Vim Tux (Portable) available.

8.0.005 | Updated: 16 Sep 2016

Downloads:

122,386

Downloads of v 8.0.005:

503

Maintainer(s):

Pauby

Software Author(s):

Build: TuxProject.de
Developer: vim team

Tags:

vim-tux vim editor tux

Vim Tux (Portable) 8.0.005

This is not the latest version of Vim Tux (Portable) available.

Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Build: TuxProject.de, Developer: vim team. The inclusion of Build: TuxProject.de, Developer: vim team trademark(s), if any, upon this webpage is solely to identify Build: TuxProject.de, Developer: vim team goods or services and not for commercial purposes.

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Hide Checks

Validation Testing Passed

Verification Testing Passed

Details

Scan 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.

Details

Learn More

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:

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

Option 2: Internalized Package (Reliable, Scalable)

Open Source
- Download the package:
  Download
- Follow manual internalization instructions

Package Internalizer (C4B)

Run: (additional options)

choco download vim-tux.portable --internalize --version=8.0.005 --source=https://community.chocolatey.org/api/v2/

For package and dependencies run:

choco push --source="'INTERNAL REPO URL'"

Automate package internalization

3. Copy Your Script

choco upgrade vim-tux.portable -y --source="'INTERNAL REPO URL'" --version="'8.0.005'" [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.0.005'" 
$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.0.005'
    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.0.005'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller vim-tux.portable
{
    Name     = "vim-tux.portable"
    Version  = "8.0.005"
    Source   = "INTERNAL REPO URL"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'vim-tux.portable':
  ensure   => '8.0.005',
  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.

NOTE

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

NOTE

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.

WARNING

There are versions of this package awaiting moderation . See the Version History section below.

Package Approved

This package was approved as a trusted package on 16 Sep 2016.

Description

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.

Files

tools\chocolateyinstall.ps1

$packageName = 'vim-tux.portable'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$destDir = Join-Path $toolsDir "vim80"
$url = "https://tuxproject.de/projects/vim/complete-x86.7z"
$url64 = "https://tuxproject.de/projects/vim/complete-x64.7z"

Get-ChildItem "$destDir\*.bat" | %{ Install-BinFile -Name $_.BaseName -Path $_ }
Install-ChocolateyZipPackage $packageName $url $destDir $url64
Start-Process "$destDir\install.exe" -ArgumentList "-add-start-menu" -WorkingDirectory "$destDir" -Wait
Write-Output "Build provided by TuxProject.de - consider donating to help support their server costs."

tools\chocolateyuninstall.ps1

$packageName = 'vim-tux.portable'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$destDir = Join-Path $toolsDir "vim80"

Get-ChildItem "$destDir\*.bat" | %{ Uninstall-BinFile -Name $_.BaseName -Path $_ }
Start-Process "$destDir\uninstal.exe" -ArgumentList "-nsis" -Wait

tools\vim80\evim.bat

@echo off
rem -- Run Vim --

set VIM_EXE_DIR=%ChocolateyInstall%\lib\vim-tux.portable\tools\vim74
if exist "%VIM%\vim74\gvim.exe" set VIM_EXE_DIR=%VIM%\vim74
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==.-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=

tools\vim80\gview.bat

@echo off
rem -- Run Vim --

set VIM_EXE_DIR=%ChocolateyInstall%\lib\vim-tux.portable\tools\vim74
if exist "%VIM%\vim74\gvim.exe" set VIM_EXE_DIR=%VIM%\vim74
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==.-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=

tools\vim80\gvim.exe.gui

tools\vim80\gvimdiff.bat

@echo off
rem -- Run Vim --

set VIM_EXE_DIR=%ChocolateyInstall%\lib\vim-tux.portable\tools\vim74
if exist "%VIM%\vim74\gvim.exe" set VIM_EXE_DIR=%VIM%\vim74
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==.-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=

tools\vim80\install.exe.ignore

tools\vim80\tee.exe.ignore

tools\vim80\uninstal.exe.ignore

tools\vim80\view.bat

@echo off
rem -- Run Vim --

set VIM_EXE_DIR=%ChocolateyInstall%\lib\vim-tux.portable\tools\vim74
if exist "%VIM%\vim74\vim.exe" set VIM_EXE_DIR=%VIM%\vim74
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=

tools\vim80\vimdiff.bat

@echo off
rem -- Run Vim --

set VIM_EXE_DIR=%ChocolateyInstall%\lib\vim-tux.portable\tools\vim74
if exist "%VIM%\vim74\vim.exe" set VIM_EXE_DIR=%VIM%\vim74
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=

tools\vim80\vimrun.exe.ignore

tools\vim80\xxd.exe.ignore

Virus Scan Results

VisVim.dll (f522b9acbd38) - ## / 68
gvim.exe (318910496f9b) - ## / 57
gvim_noOLE.exe (85cbf47bf22f) - ## / 57
install.exe (c7b4e6b4edec) - ## / 58
tee.exe (999678ef18ea) - ## / 57
uninstal.exe (57735c17eeca) - ## / 57
vim.exe (be10424b4863) - ## / 56
vimrun.exe (ab2482323f20) - ## / 58
xxd.exe (856dc1491bf6) - ## / 57
gvimext.dll (dcb658810b15) - ## / 57
gvim.exe (d327f9849092) - ## / 57
gvim_noOLE.exe (cc37857fdca9) - ## / 57
install.exe (59da2a48e8e1) - ## / 57
tee.exe (d18e5e24a09b) - ## / 57
uninstal.exe (fcf42b83082a) - ## / 57
vim.exe (fd9bb757d785) - ## / 57
vimrun.exe (e7a19083ccf7) - ## / 57
xxd.exe (4d3fe34bf57d) - ## / 57
gvimext.dll (ff78191d246f) - ## / 57
complete-x64.7z (ecbe4a1bf98a) - ## / 53
complete-x86.7z (f39762242473) - ## / 53
vim-tux.portable.8.0.005.nupkg (5034099e7e42) - ## / 56

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.

Version History

Version	Downloads	Last Updated	Status
Vim Tux (Portable) 9.1.1508	7	Friday, July 4, 2025	Approved
Vim Tux (Portable) 9.1.1503	13	Wednesday, July 2, 2025	Approved
Vim Tux (Portable) 9.1.1497	6	Tuesday, July 1, 2025	Waiting for Maintainer
Vim Tux (Portable) 9.1.1484	18	Friday, June 27, 2025	Approved
Vim Tux (Portable) 9.1.1481	13	Thursday, June 26, 2025	Approved
Vim Tux (Portable) 9.1.1478	16	Wednesday, June 25, 2025	Approved
Vim Tux (Portable) 9.1.1473	19	Saturday, June 21, 2025	Approved
Vim Tux (Portable) 9.1.1472	17	Friday, June 20, 2025	Approved
Vim Tux (Portable) 9.1.1466	8	Wednesday, June 18, 2025	Waiting for Maintainer
Vim Tux (Portable) 9.1.1465	15	Tuesday, June 17, 2025	Approved
Vim Tux (Portable) 9.1.1460	16	Monday, June 16, 2025	Approved
Vim Tux (Portable) 9.1.1455	9	Friday, June 13, 2025	Waiting for Maintainer
Vim Tux (Portable) 9.1.1453	22	Thursday, June 12, 2025	Approved
Vim Tux (Portable) 9.1.1446	13	Tuesday, June 10, 2025	Approved
Vim Tux (Portable) 9.1.1432	13	Friday, June 6, 2025	Waiting for Maintainer
Vim Tux (Portable) 9.1.1429	18	Wednesday, June 4, 2025	Approved
Vim Tux (Portable) 9.1.1425	15	Tuesday, June 3, 2025	Approved
Vim Tux (Portable) 9.1.1418	17	Friday, May 30, 2025	Approved
Vim Tux (Portable) 9.1.1414	19	Tuesday, May 27, 2025	Approved
Vim Tux (Portable) 9.1.1401	20	Friday, May 23, 2025	Approved
Vim Tux (Portable) 9.1.1393	604	Saturday, May 17, 2025	Approved
Vim Tux (Portable) 9.1.1385	24	Tuesday, May 13, 2025	Approved
Vim Tux (Portable) 9.1.1382	19	Monday, May 12, 2025	Approved
Vim Tux (Portable) 9.1.1370	19	Thursday, May 8, 2025	Approved
Vim Tux (Portable) 9.1.1365	20	Monday, May 5, 2025	Approved
Vim Tux (Portable) 9.1.1355	23	Wednesday, April 30, 2025	Approved
Vim Tux (Portable) 9.1.1346	26	Saturday, April 26, 2025	Approved
Vim Tux (Portable) 9.1.1336	25	Wednesday, April 23, 2025	Approved
Vim Tux (Portable) 9.1.1330	27	Tuesday, April 22, 2025	Approved
Vim Tux (Portable) 9.1.1308	26	Wednesday, April 16, 2025	Approved
Vim Tux (Portable) 9.1.1288	33	Wednesday, April 9, 2025	Approved
Vim Tux (Portable) 9.1.1283	27	Tuesday, April 8, 2025	Approved
Vim Tux (Portable) 9.1.1267	27	Thursday, April 3, 2025	Approved
Vim Tux (Portable) 9.1.1263	28	Monday, March 31, 2025	Approved
Vim Tux (Portable) 9.1.1232	31	Monday, March 24, 2025	Approved
Vim Tux (Portable) 9.1.1227	36	Saturday, March 22, 2025	Approved
Vim Tux (Portable) 9.1.1224	34	Wednesday, March 19, 2025	Approved
Vim Tux (Portable) 9.1.1199	34	Thursday, March 13, 2025	Approved
Vim Tux (Portable) 9.1.1194	32	Wednesday, March 12, 2025	Approved
Vim Tux (Portable) 9.1.1186	24	Sunday, March 9, 2025	Approved
Vim Tux (Portable) 9.1.1166	33	Monday, March 3, 2025	Approved
Vim Tux (Portable) 9.1.1144	34	Monday, February 24, 2025	Approved
Vim Tux (Portable) 9.1.1129	34	Friday, February 21, 2025	Approved
Vim Tux (Portable) 9.1.1122	27	Thursday, February 20, 2025	Approved
Vim Tux (Portable) 9.1.1119	33	Tuesday, February 18, 2025	Approved
Vim Tux (Portable) 9.1.1117	27	Monday, February 17, 2025	Approved
Vim Tux (Portable) 9.1.1106	24	Thursday, February 13, 2025	Approved
Vim Tux (Portable) 9.1.1071	41	Monday, February 3, 2025	Approved
Vim Tux (Portable) 9.1.1056	31	Thursday, January 30, 2025	Approved
Vim Tux (Portable) 9.1.1046	57	Thursday, January 23, 2025	Approved
Vim Tux (Portable) 9.1.1043	41	Wednesday, January 22, 2025	Approved
Vim Tux (Portable) 9.1.1039	43	Tuesday, January 21, 2025	Approved
Vim Tux (Portable) 9.1.1012	42	Monday, January 13, 2025	Approved
Vim Tux (Portable) 9.1.1000	43	Friday, January 10, 2025	Approved
Vim Tux (Portable) 9.1.998	41	Thursday, January 9, 2025	Approved
Vim Tux (Portable) 9.1.990	46	Tuesday, January 7, 2025	Approved
Vim Tux (Portable) 9.1.980	47	Monday, December 30, 2024	Approved
Vim Tux (Portable) 9.1.942	52	Wednesday, December 18, 2024	Approved
Vim Tux (Portable) 9.1.923	56	Saturday, December 14, 2024	Approved
Vim Tux (Portable) 9.1.899	54	Monday, December 2, 2024	Approved
Vim Tux (Portable) 9.1.892	47	Friday, November 29, 2024	Approved
Vim Tux (Portable) 9.1.888	47	Tuesday, November 26, 2024	Approved
Vim Tux (Portable) 9.1.861	60	Wednesday, November 13, 2024	Approved
Vim Tux (Portable) 9.1.849	45	Monday, November 11, 2024	Approved
Vim Tux (Portable) 9.1.847	63	Friday, November 8, 2024	Approved
Vim Tux (Portable) 9.1.837	46	Monday, November 4, 2024	Approved
Vim Tux (Portable) 9.1.818	51	Monday, October 28, 2024	Approved
Vim Tux (Portable) 9.1.813	52	Thursday, October 24, 2024	Approved
Vim Tux (Portable) 9.1.810	45	Thursday, October 24, 2024	Approved
Vim Tux (Portable) 9.1.792	53	Saturday, October 19, 2024	Approved
Vim Tux (Portable) 9.1.785	56	Tuesday, October 15, 2024	Approved
Vim Tux (Portable) 9.1.766	58	Wednesday, October 9, 2024	Approved
Vim Tux (Portable) 9.1.758	71	Saturday, October 5, 2024	Approved
Vim Tux (Portable) 9.1.757	52	Friday, October 4, 2024	Approved
Vim Tux (Portable) 9.1.736	69	Wednesday, September 18, 2024	Approved
Vim Tux (Portable) 9.1.730	69	Saturday, September 14, 2024	Approved
Vim Tux (Portable) 9.1.724	53	Wednesday, September 11, 2024	Approved
Vim Tux (Portable) 9.1.722	60	Tuesday, September 10, 2024	Approved
Vim Tux (Portable) 9.1.718	63	Friday, September 6, 2024	Approved
Vim Tux (Portable) 9.1.714	62	Thursday, September 5, 2024	Approved
Vim Tux (Portable) 9.1.708	67	Monday, September 2, 2024	Approved
Vim Tux (Portable) 9.1.697	87	Monday, August 26, 2024	Approved
Vim Tux (Portable) 9.1.689	65	Friday, August 23, 2024	Approved
Vim Tux (Portable) 9.1.685	63	Wednesday, August 21, 2024	Approved
Vim Tux (Portable) 9.1.682	50	Tuesday, August 20, 2024	Approved
Vim Tux (Portable) 9.1.675	62	Friday, August 16, 2024	Approved
Vim Tux (Portable) 9.1.668	73	Saturday, August 10, 2024	Approved
Vim Tux (Portable) 9.1.661	75	Tuesday, August 6, 2024	Approved
Vim Tux (Portable) 9.1.660	60	Monday, August 5, 2024	Approved
Vim Tux (Portable) 9.1.645	82	Thursday, August 1, 2024	Approved
Vim Tux (Portable) 9.1.643	64	Wednesday, July 31, 2024	Approved
Vim Tux (Portable) 9.1.636	71	Tuesday, July 30, 2024	Approved
Vim Tux (Portable) 9.1.608	79	Monday, July 22, 2024	Approved
Vim Tux (Portable) 9.1.602	78	Friday, July 19, 2024	Approved
Vim Tux (Portable) 9.1.598	77	Friday, July 19, 2024	Approved
Vim Tux (Portable) 9.1.586	74	Tuesday, July 16, 2024	Approved
Vim Tux (Portable) 9.1.571	68	Friday, July 12, 2024	Approved
Vim Tux (Portable) 9.1.554	80	Thursday, July 11, 2024	Approved
Vim Tux (Portable) 9.1.546	61	Tuesday, July 9, 2024	Approved
Vim Tux (Portable) 9.1.544	70	Tuesday, July 9, 2024	Approved
Vim Tux (Portable) 9.1.531	65	Saturday, July 6, 2024	Approved
Vim Tux (Portable) 9.1.516	81	Monday, June 24, 2024	Approved
Vim Tux (Portable) 9.1.514	80	Saturday, June 22, 2024	Approved
Vim Tux (Portable) 9.1.505	58	Thursday, June 20, 2024	Approved
Vim Tux (Portable) 9.1.500	65	Wednesday, June 19, 2024	Approved
Vim Tux (Portable) 9.1.496	72	Tuesday, June 18, 2024	Approved
Vim Tux (Portable) 9.1.491	77	Saturday, June 15, 2024	Approved
Vim Tux (Portable) 9.1.487	75	Saturday, June 15, 2024	Approved
Vim Tux (Portable) 9.1.478	72	Thursday, June 13, 2024	Approved
Vim Tux (Portable) 9.1.474	58	Tuesday, June 11, 2024	Approved
Vim Tux (Portable) 9.1.472	70	Monday, June 10, 2024	Approved
Vim Tux (Portable) 9.1.470	72	Thursday, June 6, 2024	Approved
Vim Tux (Portable) 9.1.466	81	Thursday, June 6, 2024	Approved
Vim Tux (Portable) 9.1.461	71	Tuesday, June 4, 2024	Approved
Vim Tux (Portable) 9.1.454	84	Saturday, June 1, 2024	Approved
Vim Tux (Portable) 9.1.448	71	Thursday, May 30, 2024	Approved
Vim Tux (Portable) 9.1.447	80	Tuesday, May 28, 2024	Approved
Vim Tux (Portable) 9.1.442	84	Saturday, May 25, 2024	Approved
Vim Tux (Portable) 9.1.433	66	Friday, May 24, 2024	Approved
Vim Tux (Portable) 9.1.432	76	Thursday, May 23, 2024	Approved
Vim Tux (Portable) 9.1.426	83	Wednesday, May 22, 2024	Approved
Vim Tux (Portable) 9.1.412	90	Tuesday, May 21, 2024	Approved
Vim Tux (Portable) 9.1.411	67	Monday, May 13, 2024	Approved
Vim Tux (Portable) 9.1.407	73	Sunday, May 12, 2024	Approved
Vim Tux (Portable) 9.1.393	76	Wednesday, May 8, 2024	Approved
Vim Tux (Portable) 9.1.386	80	Thursday, May 2, 2024	Approved
Vim Tux (Portable) 9.1.380	85	Tuesday, April 30, 2024	Approved
Vim Tux (Portable) 9.1.369	80	Thursday, April 25, 2024	Approved
Vim Tux (Portable) 9.1.368	69	Thursday, April 25, 2024	Approved
Vim Tux (Portable) 9.1.366	78	Tuesday, April 23, 2024	Approved
Vim Tux (Portable) 9.1.363	74	Monday, April 22, 2024	Approved
Vim Tux (Portable) 9.1.354	73	Saturday, April 20, 2024	Approved
Vim Tux (Portable) 9.1.336	81	Tuesday, April 16, 2024	Approved
Vim Tux (Portable) 9.1.330	80	Monday, April 15, 2024	Approved
Vim Tux (Portable) 9.1.296	89	Thursday, April 11, 2024	Approved
Vim Tux (Portable) 9.1.193	96	Friday, March 22, 2024	Approved
Vim Tux (Portable) 9.1.186	95	Tuesday, March 19, 2024	Approved
Vim Tux (Portable) 9.1.181	80	Saturday, March 16, 2024	Approved
Vim Tux (Portable) 9.1.149	93	Tuesday, March 5, 2024	Approved
Vim Tux (Portable) 9.1.113	99	Friday, February 16, 2024	Approved
Vim Tux (Portable) 9.1.67	99	Friday, February 2, 2024	Approved
Vim Tux (Portable) 9.1.50	90	Tuesday, January 30, 2024	Approved
Vim Tux (Portable) 9.0.2181	135	Thursday, December 21, 2023	Approved
Vim Tux (Portable) 9.0.2167	91	Friday, December 15, 2023	Approved
Vim Tux (Portable) 9.0.2155	100	Saturday, December 9, 2023	Approved
Vim Tux (Portable) 9.0.2122	97	Friday, November 24, 2023	Approved
Vim Tux (Portable) 9.0.2120	92	Thursday, November 23, 2023	Approved
Vim Tux (Portable) 9.0.2105	95	Wednesday, November 15, 2023	Approved
Vim Tux (Portable) 9.0.2103	109	Tuesday, November 14, 2023	Approved
Vim Tux (Portable) 9.0.2095	95	Thursday, November 9, 2023	Approved
Vim Tux (Portable) 9.0.2092	91	Tuesday, November 7, 2023	Approved
Vim Tux (Portable) 9.0.2081	116	Wednesday, November 1, 2023	Approved
Vim Tux (Portable) 9.0.2077	99	Saturday, October 28, 2023	Approved
Vim Tux (Portable) 9.0.2063	290	Tuesday, October 24, 2023	Approved
Vim Tux (Portable) 9.0.2053	109	Friday, October 20, 2023	Approved
Vim Tux (Portable) 9.0.2050	92	Thursday, October 19, 2023	Approved
Vim Tux (Portable) 9.0.2048	109	Thursday, October 19, 2023	Approved
Vim Tux (Portable) 9.0.2043	91	Wednesday, October 18, 2023	Approved
Vim Tux (Portable) 9.0.2034	101	Tuesday, October 17, 2023	Approved
Vim Tux (Portable) 9.0.2009	90	Tuesday, October 10, 2023	Approved
Vim Tux (Portable) 9.0.1976	86	Wednesday, October 4, 2023	Approved
Vim Tux (Portable) 9.0.1943	86	Wednesday, September 27, 2023	Approved
Vim Tux (Portable) 9.0.1927	576	Thursday, September 21, 2023	Approved
Vim Tux (Portable) 9.0.1907	888	Monday, September 18, 2023	Approved
Vim Tux (Portable) 9.0.1901	652	Sunday, September 17, 2023	Approved
Vim Tux (Portable) 9.0.1897	136	Wednesday, September 13, 2023	Approved
Vim Tux (Portable) 9.0.1877	124	Friday, September 8, 2023	Exempted
Vim Tux (Portable) 9.0.1811	95	Monday, August 28, 2023	Exempted
Vim Tux (Portable) 9.0.1787	88	Monday, August 28, 2023	Approved
Vim Tux (Portable) 9.0.0846	296	Thursday, November 10, 2022	Approved
Vim Tux (Portable) 9.0.0828	119	Friday, November 4, 2022	Approved
Vim Tux (Portable) 9.0.0815	121	Wednesday, October 26, 2022	Approved
Vim Tux (Portable) 9.0.0814	111	Saturday, October 22, 2022	Approved
Vim Tux (Portable) 9.0.0806	121	Friday, October 21, 2022	Approved
Vim Tux (Portable) 9.0.0797	98	Thursday, October 20, 2022	Approved
Vim Tux (Portable) 9.0.0780	124	Tuesday, October 18, 2022	Approved
Vim Tux (Portable) 9.0.0733	131	Thursday, October 13, 2022	Approved
Vim Tux (Portable) 9.0.0715	125	Tuesday, October 11, 2022	Approved
Vim Tux (Portable) 9.0.0682	111	Saturday, October 8, 2022	Approved
Vim Tux (Portable) 9.0.656.20221005	134	Thursday, October 6, 2022	Approved
Vim Tux (Portable) 9.0.0656	119	Wednesday, October 5, 2022	Approved
Vim Tux (Portable) 8.2.3908	344	Monday, December 27, 2021	Approved
Vim Tux (Portable) 8.2.3875	132	Thursday, December 23, 2021	Approved
Vim Tux (Portable) 8.2.3858	155	Tuesday, December 21, 2021	Approved
Vim Tux (Portable) 8.2.3836	145	Saturday, December 18, 2021	Approved
Vim Tux (Portable) 8.2.3811	151	Wednesday, December 15, 2021	Approved
Vim Tux (Portable) 8.2.3794	141	Tuesday, December 14, 2021	Approved
Vim Tux (Portable) 8.2.3763	148	Friday, December 10, 2021	Approved
Vim Tux (Portable) 8.2.3757	131	Wednesday, December 8, 2021	Approved
Vim Tux (Portable) 8.2.3752	142	Tuesday, December 7, 2021	Approved
Vim Tux (Portable) 8.2.3718	148	Friday, December 3, 2021	Approved
Vim Tux (Portable) 8.2.3717	149	Thursday, December 2, 2021	Approved
Vim Tux (Portable) 8.2.3701	139	Tuesday, November 30, 2021	Approved
Vim Tux (Portable) 8.2.3692	136	Monday, November 29, 2021	Approved
Vim Tux (Portable) 8.2.3671	167	Friday, November 26, 2021	Approved
Vim Tux (Portable) 8.2.3659	144	Thursday, November 25, 2021	Approved
Vim Tux (Portable) 8.2.3651	153	Tuesday, November 23, 2021	Approved
Vim Tux (Portable) 8.2.3646	132	Tuesday, November 23, 2021	Approved
Vim Tux (Portable) 8.2.3623	141	Saturday, November 20, 2021	Approved
Vim Tux (Portable) 8.2.3608	146	Thursday, November 18, 2021	Approved
Vim Tux (Portable) 8.2.3595	135	Tuesday, November 16, 2021	Approved
Vim Tux (Portable) 8.2.3579	163	Friday, November 5, 2021	Approved
Vim Tux (Portable) 8.2.3565	152	Wednesday, October 27, 2021	Approved
Vim Tux (Portable) 8.2.3551	140	Friday, October 22, 2021	Approved
Vim Tux (Portable) 8.2.3545	137	Thursday, October 21, 2021	Approved
Vim Tux (Portable) 8.2.3532	135	Tuesday, October 19, 2021	Approved
Vim Tux (Portable) 8.2.3513	159	Saturday, October 16, 2021	Approved
Vim Tux (Portable) 8.2.3505	133	Thursday, October 14, 2021	Approved
Vim Tux (Portable) 8.2.3493	143	Tuesday, October 12, 2021	Approved
Vim Tux (Portable) 8.2.3486	125	Saturday, October 9, 2021	Approved
Vim Tux (Portable) 8.2.3484	134	Thursday, October 7, 2021	Approved
Vim Tux (Portable) 8.2.3478	140	Wednesday, October 6, 2021	Approved
Vim Tux (Portable) 8.2.3469	146	Tuesday, October 5, 2021	Approved
Vim Tux (Portable) 8.2.3458	147	Tuesday, September 28, 2021	Approved
Vim Tux (Portable) 8.2.3455	137	Thursday, September 23, 2021	Approved
Vim Tux (Portable) 8.2.3450	149	Tuesday, September 21, 2021	Approved
Vim Tux (Portable) 8.2.3448	142	Sunday, September 19, 2021	Approved
Vim Tux (Portable) 8.2.3434	154	Tuesday, September 14, 2021	Approved
Vim Tux (Portable) 8.2.3416	157	Thursday, September 9, 2021	Approved
Vim Tux (Portable) 8.2.3394	146	Thursday, September 2, 2021	Approved
Vim Tux (Portable) 8.2.3391	162	Wednesday, September 1, 2021	Approved
Vim Tux (Portable) 8.2.3376	177	Friday, August 27, 2021	Approved
Vim Tux (Portable) 8.2.3358	158	Friday, August 20, 2021	Approved
Vim Tux (Portable) 8.2.3356	140	Wednesday, August 18, 2021	Approved
Vim Tux (Portable) 8.2.3326	200	Wednesday, August 11, 2021	Approved
Vim Tux (Portable) 8.2.3318	158	Monday, August 9, 2021	Approved
Vim Tux (Portable) 8.2.3299	149	Friday, August 6, 2021	Approved
Vim Tux (Portable) 8.2.3290	131	Thursday, August 5, 2021	Approved
Vim Tux (Portable) 8.2.3281	153	Wednesday, August 4, 2021	Approved
Vim Tux (Portable) 8.2.3273	155	Tuesday, August 3, 2021	Approved
Vim Tux (Portable) 8.2.3269	157	Monday, August 2, 2021	Approved
Vim Tux (Portable) 8.2.3263	131	Sunday, August 1, 2021	Approved
Vim Tux (Portable) 8.2.3253	167	Saturday, July 31, 2021	Approved
Vim Tux (Portable) 8.2.3242	143	Thursday, July 29, 2021	Approved
Vim Tux (Portable) 8.2.3223	138	Tuesday, July 27, 2021	Approved
Vim Tux (Portable) 8.2.3204	145	Friday, July 23, 2021	Approved
Vim Tux (Portable) 8.2.3187	147	Tuesday, July 20, 2021	Approved
Vim Tux (Portable) 8.2.3171	160	Friday, July 16, 2021	Approved
Vim Tux (Portable) 8.2.3158	175	Wednesday, July 14, 2021	Approved
Vim Tux (Portable) 8.2.3131	144	Friday, July 9, 2021	Approved
Vim Tux (Portable) 8.2.3120	161	Thursday, July 8, 2021	Approved
Vim Tux (Portable) 8.2.3113	149	Wednesday, July 7, 2021	Approved
Vim Tux (Portable) 8.2.3107	144	Tuesday, July 6, 2021	Approved
Vim Tux (Portable) 8.2.3104	146	Monday, July 5, 2021	Approved
Vim Tux (Portable) 8.2.3095	156	Sunday, July 4, 2021	Approved
Vim Tux (Portable) 8.2.3080	147	Thursday, July 1, 2021	Approved
Vim Tux (Portable) 8.2.3075	149	Wednesday, June 30, 2021	Approved
Vim Tux (Portable) 8.2.3066	157	Monday, June 28, 2021	Approved
Vim Tux (Portable) 8.2.3055	142	Sunday, June 27, 2021	Approved
Vim Tux (Portable) 8.2.3043	149	Thursday, June 24, 2021	Approved
Vim Tux (Portable) 8.2.3033	149	Tuesday, June 22, 2021	Approved
Vim Tux (Portable) 8.2.3020	131	Sunday, June 20, 2021	Approved
Vim Tux (Portable) 8.2.3017	156	Friday, June 18, 2021	Approved
Vim Tux (Portable) 8.2.2840	197	Saturday, May 8, 2021	Approved
Vim Tux (Portable) 8.2.2832	168	Wednesday, May 5, 2021	Approved
Vim Tux (Portable) 8.2.2815	206	Wednesday, April 28, 2021	Approved
Vim Tux (Portable) 8.2.2799	213	Thursday, April 22, 2021	Approved
Vim Tux (Portable) 8.2.2794	156	Wednesday, April 21, 2021	Approved
Vim Tux (Portable) 8.2.2763	169	Thursday, April 15, 2021	Approved
Vim Tux (Portable) 8.2.2738	167	Friday, April 9, 2021	Approved
Vim Tux (Portable) 8.2.2730	190	Wednesday, April 7, 2021	Approved
Vim Tux (Portable) 8.2.2679	167	Wednesday, March 31, 2021	Approved
Vim Tux (Portable) 8.2.2650	160	Friday, March 26, 2021	Approved
Vim Tux (Portable) 8.2.2648	176	Wednesday, March 24, 2021	Approved
Vim Tux (Portable) 8.2.2637	153	Tuesday, March 23, 2021	Approved
Vim Tux (Portable) 8.2.2491	241	Thursday, February 11, 2021	Approved
Vim Tux (Portable) 8.2.2129	250	Saturday, December 12, 2020	Approved
Vim Tux (Portable) 8.2.1981	196	Saturday, November 14, 2020	Approved
Vim Tux (Portable) 8.2.1955	204	Friday, November 6, 2020	Approved
Vim Tux (Portable) 8.2.1923	217	Friday, October 30, 2020	Approved
Vim Tux (Portable) 8.2.1883	204	Thursday, October 22, 2020	Approved
Vim Tux (Portable) 8.2.1858	190	Sunday, October 18, 2020	Approved
Vim Tux (Portable) 8.2.1738	247	Friday, September 25, 2020	Approved
Vim Tux (Portable) 8.2.1651	227	Thursday, September 10, 2020	Approved
Vim Tux (Portable) 8.2.1058	295	Friday, June 26, 2020	Approved
Vim Tux (Portable) 8.2.1007	221	Friday, June 19, 2020	Approved
Vim Tux (Portable) 8.2.988	268	Wednesday, June 17, 2020	Approved
Vim Tux (Portable) 8.2.960	223	Friday, June 12, 2020	Approved
Vim Tux (Portable) 8.2.950	223	Thursday, June 11, 2020	Approved
Vim Tux (Portable) 8.2.916	248	Sunday, June 7, 2020	Approved
Vim Tux (Portable) 8.2.882	227	Tuesday, June 2, 2020	Approved
Vim Tux (Portable) 8.2.855	216	Sunday, May 31, 2020	Approved
Vim Tux (Portable) 8.2.834	244	Friday, May 29, 2020	Approved
Vim Tux (Portable) 8.2.829	252	Wednesday, May 27, 2020	Approved
Vim Tux (Portable) 8.2.821	199	Tuesday, May 26, 2020	Approved
Vim Tux (Portable) 8.2.806	232	Friday, May 22, 2020	Approved
Vim Tux (Portable) 8.2.803	212	Thursday, May 21, 2020	Approved
Vim Tux (Portable) 8.2.766	243	Sunday, May 17, 2020	Approved
Vim Tux (Portable) 8.2.750	238	Thursday, May 14, 2020	Approved
Vim Tux (Portable) 8.2.735	243	Tuesday, May 12, 2020	Approved
Vim Tux (Portable) 8.2.647	283	Monday, April 27, 2020	Approved
Vim Tux (Portable) 8.2.640	205	Sunday, April 26, 2020	Approved
Vim Tux (Portable) 8.2.625	222	Friday, April 24, 2020	Approved
Vim Tux (Portable) 8.2.612	292	Tuesday, April 21, 2020	Approved
Vim Tux (Portable) 8.2.592	235	Saturday, April 18, 2020	Approved
Vim Tux (Portable) 8.2.585	206	Friday, April 17, 2020	Approved
Vim Tux (Portable) 8.2.577	253	Tuesday, April 14, 2020	Approved
Vim Tux (Portable) 8.2.0536	237	Sunday, April 12, 2020	Approved
Vim Tux (Portable) 8.2.0515	251	Monday, April 6, 2020	Approved
Vim Tux (Portable) 8.2.0505	240	Saturday, April 4, 2020	Approved
Vim Tux (Portable) 8.2.0486	222	Wednesday, April 1, 2020	Approved
Vim Tux (Portable) 8.2.0464	248	Sunday, March 29, 2020	Approved
Vim Tux (Portable) 8.2.0397	261	Wednesday, March 18, 2020	Approved
Vim Tux (Portable) 8.2.0369	287	Wednesday, March 11, 2020	Approved
Vim Tux (Portable) 8.2.0357	271	Friday, March 6, 2020	Approved
Vim Tux (Portable) 8.2.0324	257	Friday, February 28, 2020	Approved
Vim Tux (Portable) 8.2.0313	238	Monday, February 24, 2020	Approved
Vim Tux (Portable) 8.2.0294	226	Saturday, February 22, 2020	Approved
Vim Tux (Portable) 8.2.0285	208	Friday, February 21, 2020	Approved
Vim Tux (Portable) 8.2.0273	244	Tuesday, February 18, 2020	Approved
Vim Tux (Portable) 8.2.0231	281	Sunday, February 9, 2020	Approved
Vim Tux (Portable) 8.2.0164	262	Wednesday, January 29, 2020	Approved
Vim Tux (Portable) 8.2.0147	200	Saturday, January 25, 2020	Approved
Vim Tux (Portable) 8.2.0129	273	Sunday, January 19, 2020	Approved
Vim Tux (Portable) 8.2.0114	233	Tuesday, January 14, 2020	Approved
Vim Tux (Portable) 8.2.0109	217	Friday, January 10, 2020	Approved
Vim Tux (Portable) 8.2.0092	259	Tuesday, January 7, 2020	Approved
Vim Tux (Portable) 8.2.0080	263	Friday, January 3, 2020	Approved
Vim Tux (Portable) 8.2.0065	258	Tuesday, December 31, 2019	Approved
Vim Tux (Portable) 8.2.0055	217	Monday, December 30, 2019	Approved
Vim Tux (Portable) 8.2.0052	245	Sunday, December 29, 2019	Approved
Vim Tux (Portable) 8.2.0033	233	Tuesday, December 24, 2019	Approved
Vim Tux (Portable) 8.2.0021	220	Thursday, December 19, 2019	Approved
Vim Tux (Portable) 8.2.0011	235	Monday, December 16, 2019	Approved
Vim Tux (Portable) 8.1.2333	301	Friday, November 22, 2019	Approved
Vim Tux (Portable) 8.1.2323	295	Thursday, November 21, 2019	Approved
Vim Tux (Portable) 8.1.2311	289	Sunday, November 17, 2019	Approved
Vim Tux (Portable) 8.1.2300	245	Thursday, November 14, 2019	Approved
Vim Tux (Portable) 8.1.2237	279	Friday, November 1, 2019	Approved
Vim Tux (Portable) 8.1.2204	328	Thursday, October 24, 2019	Approved
Vim Tux (Portable) 8.1.2200	262	Wednesday, October 23, 2019	Approved
Vim Tux (Portable) 8.1.2148	282	Monday, October 14, 2019	Approved
Vim Tux (Portable) 8.1.2133	239	Friday, October 11, 2019	Approved
Vim Tux (Portable) 8.1.2117	269	Sunday, October 6, 2019	Approved
Vim Tux (Portable) 8.1.2108	285	Thursday, October 3, 2019	Approved
Vim Tux (Portable) 8.1.2103	222	Tuesday, October 1, 2019	Approved
Vim Tux (Portable) 8.1.2079	295	Friday, September 27, 2019	Approved
Vim Tux (Portable) 8.1.2071	218	Wednesday, September 25, 2019	Approved
Vim Tux (Portable) 8.1.2052	244	Thursday, September 19, 2019	Approved
Vim Tux (Portable) 8.1.2019	295	Tuesday, September 10, 2019	Approved
Vim Tux (Portable) 8.1.2004	263	Sunday, September 8, 2019	Approved
Vim Tux (Portable) 8.1.1995	240	Saturday, September 7, 2019	Approved
Vim Tux (Portable) 8.1.1986	252	Thursday, September 5, 2019	Approved
Vim Tux (Portable) 8.1.1961	251	Monday, September 2, 2019	Approved
Vim Tux (Portable) 8.1.1927	290	Monday, August 26, 2019	Approved
Vim Tux (Portable) 8.1.1915	240	Saturday, August 24, 2019	Approved
Vim Tux (Portable) 8.1.1906	273	Thursday, August 22, 2019	Approved
Vim Tux (Portable) 8.1.1890	232	Tuesday, August 20, 2019	Approved
Vim Tux (Portable) 8.1.1836	298	Sunday, August 11, 2019	Approved
Vim Tux (Portable) 8.1.1813	297	Monday, August 5, 2019	Approved
Vim Tux (Portable) 8.1.1744	253	Thursday, July 25, 2019	Approved
Vim Tux (Portable) 8.1.1729	250	Tuesday, July 23, 2019	Approved
Vim Tux (Portable) 8.1.1713	262	Friday, July 19, 2019	Approved
Vim Tux (Portable) 8.1.1695	259	Tuesday, July 16, 2019	Approved
Vim Tux (Portable) 8.1.1669	243	Saturday, July 13, 2019	Approved
Vim Tux (Portable) 8.1.1655	292	Tuesday, July 9, 2019	Approved
Vim Tux (Portable) 8.1.1631	247	Friday, July 5, 2019	Approved
Vim Tux (Portable) 8.1.1601	312	Thursday, June 27, 2019	Approved
Vim Tux (Portable) 8.1.1578	258	Saturday, June 22, 2019	Approved
Vim Tux (Portable) 8.1.1573	295	Thursday, June 20, 2019	Approved
Vim Tux (Portable) 8.1.1566	237	Tuesday, June 18, 2019	Approved
Vim Tux (Portable) 8.1.1557	281	Monday, June 17, 2019	Approved
Vim Tux (Portable) 8.1.1536	222	Sunday, June 16, 2019	Approved
Vim Tux (Portable) 8.1.1523	267	Friday, June 14, 2019	Approved
Vim Tux (Portable) 8.1.1515	275	Tuesday, June 11, 2019	Approved
Vim Tux (Portable) 8.1.1511	273	Monday, June 10, 2019	Approved
Vim Tux (Portable) 8.1.1455	256	Monday, June 3, 2019	Approved
Vim Tux (Portable) 8.1.1432	302	Friday, May 31, 2019	Approved
Vim Tux (Portable) 8.1.1413	301	Tuesday, May 28, 2019	Approved
Vim Tux (Portable) 8.1.1373	304	Friday, May 24, 2019	Approved
Vim Tux (Portable) 8.1.1364	285	Thursday, May 23, 2019	Approved
Vim Tux (Portable) 8.1.1353	240	Monday, May 20, 2019	Approved
Vim Tux (Portable) 8.1.1333	292	Thursday, May 16, 2019	Approved
Vim Tux (Portable) 8.1.1328	245	Monday, May 13, 2019	Approved
Vim Tux (Portable) 8.1.1312	248	Saturday, May 11, 2019	Approved
Vim Tux (Portable) 8.1.1298	275	Thursday, May 9, 2019	Approved
Vim Tux (Portable) 8.1.1286	298	Tuesday, May 7, 2019	Approved
Vim Tux (Portable) 8.1.1197	303	Monday, April 22, 2019	Approved
Vim Tux (Portable) 8.1.1183	270	Thursday, April 18, 2019	Approved
Vim Tux (Portable) 8.1.1165	265	Sunday, April 14, 2019	Approved
Vim Tux (Portable) 8.1.1140	257	Tuesday, April 9, 2019	Approved
Vim Tux (Portable) 8.1.1136	257	Monday, April 8, 2019	Approved
Vim Tux (Portable) 8.1.1124	258	Sunday, April 7, 2019	Approved
Vim Tux (Portable) 8.1.1103	295	Thursday, April 4, 2019	Approved
Vim Tux (Portable) 8.1.1097	302	Monday, April 1, 2019	Approved
Vim Tux (Portable) 8.1.1073	223	Saturday, March 30, 2019	Approved
Vim Tux (Portable) 8.1.1057	300	Thursday, March 28, 2019	Approved
Vim Tux (Portable) 8.1.1032	313	Friday, March 22, 2019	Approved
Vim Tux (Portable) 8.1.1027	305	Thursday, March 21, 2019	Approved
Vim Tux (Portable) 8.1.1017	239	Tuesday, March 19, 2019	Approved
Vim Tux (Portable) 8.1.1004	268	Monday, March 11, 2019	Approved
Vim Tux (Portable) 8.1.998	256	Friday, March 8, 2019	Approved
Vim Tux (Portable) 8.1.990	297	Sunday, March 3, 2019	Approved
Vim Tux (Portable) 8.1.984	272	Thursday, February 28, 2019	Approved
Vim Tux (Portable) 8.1.978	271	Saturday, February 23, 2019	Approved
Vim Tux (Portable) 8.1.966	286	Friday, February 22, 2019	Approved
Vim Tux (Portable) 8.1.947	267	Tuesday, February 19, 2019	Approved
Vim Tux (Portable) 8.1.934	207	Sunday, February 17, 2019	Approved
Vim Tux (Portable) 8.1.926	279	Saturday, February 16, 2019	Approved
Vim Tux (Portable) 8.1.909	256	Thursday, February 14, 2019	Approved
Vim Tux (Portable) 8.1.895	268	Tuesday, February 12, 2019	Approved
Vim Tux (Portable) 8.1.0885	271	Sunday, February 10, 2019	Approved
Vim Tux (Portable) 8.1.0877	297	Thursday, February 7, 2019	Approved
Vim Tux (Portable) 8.1.0871	271	Monday, February 4, 2019	Approved
Vim Tux (Portable) 8.1.0868	294	Sunday, February 3, 2019	Approved
Vim Tux (Portable) 8.1.0865	241	Saturday, February 2, 2019	Approved
Vim Tux (Portable) 8.1.0842	277	Thursday, January 31, 2019	Approved
Vim Tux (Portable) 8.1.0837	297	Monday, January 28, 2019	Approved
Vim Tux (Portable) 8.1.0814	280	Friday, January 25, 2019	Approved
Vim Tux (Portable) 8.1.0796	276	Thursday, January 24, 2019	Approved
Vim Tux (Portable) 8.1.0788	271	Tuesday, January 22, 2019	Approved
Vim Tux (Portable) 8.1.0757	329	Thursday, January 17, 2019	Approved
Vim Tux (Portable) 8.1.0749	260	Tuesday, January 15, 2019	Approved
Vim Tux (Portable) 8.1.0727	249	Saturday, January 12, 2019	Approved
Vim Tux (Portable) 8.1.0712	316	Thursday, January 10, 2019	Approved
Vim Tux (Portable) 8.1.0700	267	Tuesday, January 8, 2019	Approved
Vim Tux (Portable) 8.1.0690	357	Saturday, January 5, 2019	Approved
Vim Tux (Portable) 8.1.0681	307	Thursday, January 3, 2019	Approved
Vim Tux (Portable) 8.1.0674	270	Wednesday, January 2, 2019	Approved
Vim Tux (Portable) 8.1.0647	311	Friday, December 28, 2018	Approved
Vim Tux (Portable) 8.1.0644	271	Thursday, December 27, 2018	Approved
Vim Tux (Portable) 8.1.0635	239	Wednesday, December 26, 2018	Approved
Vim Tux (Portable) 8.1.0630	276	Tuesday, December 25, 2018	Approved
Vim Tux (Portable) 8.1.0629	258	Monday, December 24, 2018	Approved
Vim Tux (Portable) 8.1.0622	257	Sunday, December 23, 2018	Approved
Vim Tux (Portable) 8.1.0617	284	Saturday, December 22, 2018	Approved
Vim Tux (Portable) 8.1.0594	266	Sunday, December 16, 2018	Approved
Vim Tux (Portable) 8.1.0577	282	Thursday, December 13, 2018	Approved
Vim Tux (Portable) 8.1.0551	295	Friday, November 30, 2018	Approved
Vim Tux (Portable) 8.1.0547	305	Monday, November 26, 2018	Approved
Vim Tux (Portable) 8.1.0536	292	Tuesday, November 20, 2018	Approved
Vim Tux (Portable) 8.1.0524	293	Tuesday, November 13, 2018	Approved
Vim Tux (Portable) 8.1.0513	304	Thursday, November 8, 2018	Approved
Vim Tux (Portable) 8.1.0509	289	Sunday, November 4, 2018	Approved
Vim Tux (Portable) 8.1.0498	272	Sunday, October 28, 2018	Approved
Vim Tux (Portable) 8.1.0489	321	Monday, October 22, 2018	Approved
Vim Tux (Portable) 8.1.0474	302	Monday, October 15, 2018	Approved
Vim Tux (Portable) 8.1.0470	298	Friday, October 12, 2018	Approved
Vim Tux (Portable) 8.1.0451	350	Friday, October 5, 2018	Approved
Vim Tux (Portable) 8.1.0442	299	Monday, October 1, 2018	Approved
Vim Tux (Portable) 8.1.0436	279	Thursday, September 27, 2018	Approved
Vim Tux (Portable) 8.1.0425	305	Saturday, September 22, 2018	Approved
Vim Tux (Portable) 8.1.0408	287	Thursday, September 20, 2018	Approved
Vim Tux (Portable) 8.1.0401	291	Tuesday, September 18, 2018	Approved
Vim Tux (Portable) 8.1.0385	319	Friday, September 14, 2018	Approved
Vim Tux (Portable) 8.1.0371	320	Thursday, September 13, 2018	Approved
Vim Tux (Portable) 8.1.0362	289	Tuesday, September 11, 2018	Approved
Vim Tux (Portable) 8.1.0354	307	Sunday, September 9, 2018	Approved
Vim Tux (Portable) 8.1.0347	285	Thursday, September 6, 2018	Approved
Vim Tux (Portable) 8.1.0342	282	Sunday, September 2, 2018	Approved
Vim Tux (Portable) 8.1.0332	303	Thursday, August 30, 2018	Approved
Vim Tux (Portable) 8.1.0327	284	Sunday, August 26, 2018	Approved
Vim Tux (Portable) 8.1.0318	290	Thursday, August 23, 2018	Approved
Vim Tux (Portable) 8.1.0301	281	Tuesday, August 21, 2018	Approved
Vim Tux (Portable) 8.1.0297	283	Monday, August 20, 2018	Approved
Vim Tux (Portable) 8.1.0288	312	Thursday, August 16, 2018	Approved
Vim Tux (Portable) 8.1.0278	298	Monday, August 13, 2018	Approved
Vim Tux (Portable) 8.1.0271	289	Sunday, August 12, 2018	Approved
Vim Tux (Portable) 8.1.0259	308	Friday, August 10, 2018	Approved
Vim Tux (Portable) 8.1.0239	328	Sunday, August 5, 2018	Approved
Vim Tux (Portable) 8.1.0229	315	Tuesday, July 31, 2018	Approved
Vim Tux (Portable) 8.1.0221	314	Sunday, July 29, 2018	Approved
Vim Tux (Portable) 8.1.0210	287	Thursday, July 26, 2018	Approved
Vim Tux (Portable) 8.1.0207	294	Tuesday, July 24, 2018	Approved
Vim Tux (Portable) 8.1.0203	317	Monday, July 23, 2018	Approved
Vim Tux (Portable) 8.1.0199	293	Saturday, July 21, 2018	Approved
Vim Tux (Portable) 8.1.0196	358	Friday, July 20, 2018	Approved
Vim Tux (Portable) 8.1.0191	283	Tuesday, July 17, 2018	Approved
Vim Tux (Portable) 8.1.0186	323	Sunday, July 15, 2018	Approved
Vim Tux (Portable) 8.1.0173	362	Tuesday, July 10, 2018	Approved
Vim Tux (Portable) 8.1.0153	341	Friday, July 6, 2018	Approved
Vim Tux (Portable) 8.1.0138	330	Tuesday, July 3, 2018	Approved
Vim Tux (Portable) 8.1.0133	298	Sunday, July 1, 2018	Approved
Vim Tux (Portable) 8.1.0126	318	Friday, June 29, 2018	Approved
Vim Tux (Portable) 8.1.0105	352	Sunday, June 24, 2018	Approved
Vim Tux (Portable) 8.1.0054	350	Thursday, June 14, 2018	Approved
Vim Tux (Portable) 8.1.0034	328	Tuesday, June 5, 2018	Approved
Vim Tux (Portable) 8.1.0022	353	Friday, May 25, 2018	Approved
Vim Tux (Portable) 8.1.0013	352	Tuesday, May 22, 2018	Approved
Vim Tux (Portable) 8.1.0009	324	Monday, May 21, 2018	Approved
Vim Tux (Portable) 8.1.0004	328	Sunday, May 20, 2018	Approved
Vim Tux (Portable) 8.1.0.20180519	363	Saturday, May 19, 2018	Approved
Vim Tux (Portable) 8.1.0000	334	Friday, May 18, 2018	Approved
Vim Tux (Portable) 8.0.1848	390	Thursday, May 17, 2018	Approved
Vim Tux (Portable) 8.0.1831	391	Monday, May 14, 2018	Approved
Vim Tux (Portable) 8.0.1820	359	Sunday, May 13, 2018	Approved
Vim Tux (Portable) 8.0.1806	381	Thursday, May 10, 2018	Approved
Vim Tux (Portable) 8.0.1799	332	Monday, May 7, 2018	Approved
Vim Tux (Portable) 8.0.1794	330	Sunday, May 6, 2018	Approved
Vim Tux (Portable) 8.0.1790	385	Friday, May 4, 2018	Approved
Vim Tux (Portable) 8.0.1788	345	Thursday, May 3, 2018	Approved
Vim Tux (Portable) 8.0.1774	402	Monday, April 30, 2018	Approved
Vim Tux (Portable) 8.0.1765	371	Thursday, April 26, 2018	Approved
Vim Tux (Portable) 8.0.1748	334	Sunday, April 22, 2018	Approved
Vim Tux (Portable) 8.0.1736	362	Friday, April 20, 2018	Approved
Vim Tux (Portable) 8.0.1727	350	Wednesday, April 18, 2018	Approved
Vim Tux (Portable) 8.0.1705	367	Saturday, April 14, 2018	Approved
Vim Tux (Portable) 8.0.1679	372	Monday, April 9, 2018	Approved
Vim Tux (Portable) 8.0.1664	335	Saturday, April 7, 2018	Approved
Vim Tux (Portable) 8.0.1655	352	Saturday, March 31, 2018	Approved
Vim Tux (Portable) 8.0.1638	390	Sunday, March 25, 2018	Approved
Vim Tux (Portable) 8.0.1626	460	Thursday, March 22, 2018	Approved
Vim Tux (Portable) 8.0.1612	373	Saturday, March 17, 2018	Approved
Vim Tux (Portable) 8.0.1601	381	Tuesday, March 13, 2018	Approved
Vim Tux (Portable) 8.0.1591	407	Friday, March 9, 2018	Approved
Vim Tux (Portable) 8.0.1563	382	Sunday, March 4, 2018	Approved
Vim Tux (Portable) 8.0.1553	384	Friday, March 2, 2018	Approved
Vim Tux (Portable) 8.0.1532	414	Sunday, February 25, 2018	Approved
Vim Tux (Portable) 8.0.1504	397	Thursday, February 15, 2018	Approved
Vim Tux (Portable) 8.0.1473	370	Thursday, February 8, 2018	Approved
Vim Tux (Portable) 8.0.1451	393	Saturday, February 3, 2018	Approved
Vim Tux (Portable) 8.0.1438	427	Tuesday, January 30, 2018	Approved
Vim Tux (Portable) 8.0.1431	397	Saturday, January 27, 2018	Approved
Vim Tux (Portable) 8.0.1428	469	Thursday, January 4, 2018	Approved
Vim Tux (Portable) 8.0.1422	399	Saturday, December 30, 2017	Approved
Vim Tux (Portable) 8.0.1390	403	Sunday, December 17, 2017	Approved
Vim Tux (Portable) 8.0.1379	394	Thursday, December 14, 2017	Approved
Vim Tux (Portable) 8.0.1376	430	Thursday, December 7, 2017	Approved
Vim Tux (Portable) 8.0.1358	459	Friday, December 1, 2017	Approved
Vim Tux (Portable) 8.0.1330	412	Thursday, November 23, 2017	Approved
Vim Tux (Portable) 8.0.1311	399	Monday, November 20, 2017	Approved
Vim Tux (Portable) 8.0.1305	397	Saturday, November 18, 2017	Approved
Vim Tux (Portable) 8.0.1272	465	Thursday, November 9, 2017	Approved
Vim Tux (Portable) 8.0.1257	376	Sunday, November 5, 2017	Approved
Vim Tux (Portable) 8.0.1203	457	Wednesday, October 18, 2017	Approved
Vim Tux (Portable) 8.0.1157	484	Friday, September 29, 2017	Approved
Vim Tux (Portable) 8.0.1088	429	Monday, September 11, 2017	Approved
Vim Tux (Portable) 8.0.1010	449	Tuesday, August 29, 2017	Approved
Vim Tux (Portable) 8.0.0987	412	Wednesday, August 23, 2017	Approved
Vim Tux (Portable) 8.0.0737	490	Thursday, July 20, 2017	Approved
Vim Tux (Portable) 8.0.0642	458	Sunday, June 18, 2017	Approved
Vim Tux (Portable) 8.0.0584	458	Wednesday, April 26, 2017	Approved
Vim Tux (Portable) 8.0.0566	376	Friday, April 21, 2017	Approved
Vim Tux (Portable) 8.0.0123	674	Friday, December 9, 2016	Approved
Vim Tux (Portable) 8.0.0117	482	Friday, December 2, 2016	Approved
Vim Tux (Portable) 8.0.0066	464	Thursday, November 10, 2016	Approved
Vim Tux (Portable) 8.0.0051	489	Friday, October 28, 2016	Approved
Vim Tux (Portable) 8.0.0045	499	Friday, October 21, 2016	Approved
Vim Tux (Portable) 8.0.0017	401	Wednesday, September 28, 2016	Approved
Vim Tux (Portable) 8.0.005	503	Friday, September 16, 2016	Approved
Vim Tux (Portable) 7.4.2222	513	Thursday, August 18, 2016	Approved
Vim Tux (Portable) 7.4.2180	481	Tuesday, August 9, 2016	Approved
Vim Tux (Portable) 7.4.2153	440	Friday, August 5, 2016	Approved
Vim Tux (Portable) 7.4.2089	463	Friday, July 22, 2016	Approved
Vim Tux (Portable) 7.4.2034	457	Friday, July 15, 2016	Approved
Vim Tux (Portable) 7.4.1987	477	Sunday, July 3, 2016	Approved
Vim Tux (Portable) 7.4.1949	467	Thursday, June 23, 2016	Approved
Vim Tux (Portable) 7.4.1913	479	Friday, June 10, 2016	Approved
Vim Tux (Portable) 7.4.1905	408	Thursday, June 9, 2016	Approved
Vim Tux (Portable) 7.4.1901	458	Tuesday, June 7, 2016	Approved
Vim Tux (Portable) 7.4.1862	382	Thursday, June 2, 2016	Approved
Vim Tux (Portable) 7.4.1856	446	Monday, May 30, 2016	Approved
Vim Tux (Portable) 7.4.1848	447	Friday, May 27, 2016	Approved
Vim Tux (Portable) 7.4.1842	428	Thursday, May 26, 2016	Approved
Vim Tux (Portable) 7.4.1832	407	Thursday, May 19, 2016	Approved
Vim Tux (Portable) 7.4.1829	512	Thursday, May 12, 2016	Approved
Vim Tux (Portable) 7.4.1824	472	Monday, May 9, 2016	Approved

Release Notes

ftp://ftp.vim.org/pub/vim/patches/8.0/README

Dependencies

This package has no dependencies.

Discussion for the Vim Tux (Portable) Package

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.

Resources

Events

Courses

122,386

503

16 Sep 2016

Vim Tux (Portable)

Vim Tux (Portable) 8.0.005

Some Checks Have Failed or Are Not Yet Complete

Deployment Method: Individual Install, Upgrade, & Uninstall

Deployment Method:

1. Enter Your Internal Repository Url

2. Setup Your Environment

1. Ensure you are set for organizational deployment

2. Get the package into your environment

3. Copy Your Script

4. If applicable - Chocolatey configuration/installation

Ground Rules: