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.2.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.2.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.2.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.2.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:

111,135

Downloads of v 9.1.1076:

5

Last Update:

05 Feb 2025

Published Date:

05 Feb 2025

Package Maintainer(s):

Pauby

Software Author(s):

TuxProject.de
Vim Team

Tags:

vim-tux vim editor tux admin

Vim Tux (Portable)

(Waiting for Maintainer to take corrective action)

9.1.1076 | Updated: 05 Feb 2025

Downloads:

111,135

Downloads of v 9.1.1076:

Published:

05 Feb 2025

Maintainer(s):

Pauby

Software Author(s):

TuxProject.de
Vim Team

Tags:

vim-tux vim editor tux admin

Vim Tux (Portable) 9.1.1076

(Waiting for Maintainer to take corrective action)

Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by TuxProject.de, Vim Team. The inclusion of TuxProject.de, Vim Team trademark(s), if any, upon this webpage is solely to identify TuxProject.de, 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 Failed

Details

Scan Testing Pending

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.

IMPORTANT

This version is in moderation and has not yet been approved. This means it doesn't show up under normal search.

Until approved, you should consider this package version unsafe - it could do very bad things to your system (it probably doesn't but you have been warned, that's why we have moderation).
This package version can change wildly over the course of moderation until it is approved. If you install it and it later has changes to this version, you will be out of sync with any changes that have been made to the package. Until approved, you should consider that this package version doesn't even exist.
You cannot install this package under normal scenarios. See How to install package version under moderation for more information.
There are also no guarantees that it will be approved.

WARNING

There are versions of this package awaiting moderation (possibly just this one). See the Version History section below.

Pauby (maintainer) on 05 Feb 2025 06:13:38 +00:00:

User 'Pauby' (maintainer) submitted package.

chocolatey-ops (reviewer) on 05 Feb 2025 06:45:18 +00:00:

vim-tux.portable has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

In the ReleaseNotes element of the nuspec file a potentially invalid Url has been found. Recommendation is to fix this URL More...

Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 05 Feb 2025 07:43:13 +00:00:

vim-tux.portable has failed automated package testing (verification).
Please visit https://gist.github.com/choco-bot/4bc57919d64ccc14449e7df5f1de8f34 for details.
The package status will be changed and will be waiting on your next actions.

NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey-community/chocolatey-test-environment
Please log in and leave a review comment if you have questions and/or comments.
If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

Description

A highly configurable text editor for efficiently creating and changing any kind of text (tux build).

Vanilla build of vim, compiled with all features enabled. 'Right click > edit with vim' support included. Vim and gVim launchers are added to PATH

Please visit the official site, docs and mailing list.
Build provided by TuxProject.de - consider donating to help support their server costs.

Notes

This is an automatically updated package. If you find it is out of date by more than a week, please contact the maintainer(s), to let the know the package is no longer updating, using:
- The 'Contact Maintainers' link on the package page, or
- The 'Package Source' link on the package page and raising an issue.

Antivirus Detections

The x86 edition was removed from the package due to consistently high AV detections stopping the package from being approved.
The embedded binaries are regularly flagged by antivirus engines. Please see these GitHub issues for information: 1, 2, 3, 4 and 5. If in doubt, do not install the package.
If you find missing versions, please check the 'Version History' section on the package page. If the versions are rejected it is likely due to very high AV counts.

Files

tools\chocolateyInstall.ps1

$ErrorActionPreference = 'Stop'

$toolsDir = Split-Path -parent $MyInvocation.MyCommand.Definition
$filename64 = "$toolsDir\complete-x64.7z"

# package parameter defaults
$destDir = Join-Path -Path $toolsDir -ChildPath 'vim'

$packageArgs = @{
    packageName    = $env:ChocolateyPackageName
    fileFullPath64 = $filename64
    destination    = $destDir
}

Get-ChocolateyUnzip @packageArgs

(Get-Item $destdir\patch.exe).LastWriteTime = (Get-Date) # exe must be newer than manifest; Supplied manifest fixes useless UAC request

# Rather than letting the installer place the batch files in C:\WINDOWS, they are included them in this package.
# They are taken from C:\Windows on a default installation of vim-tux (or the vim-tux.install package).
# Installing them in this way ensures the package is compatible with non-admin installs, as a good portable package should :)
Get-ChildItem "$destDir\*.bat" | ForEach-Object {
    Install-BinFile -Name $_.BaseName -Path $_
}

# Set the VIM environment variable for the batch files to work. Note that it's the prent directory of the VIM90 folder.
# As this is a poetable package, the user may not have admin rights. Therefore, the variable scope should be 'User'
Install-ChocolateyEnvironmentVariable -VariableName 'VIM' -VariableValue $toolsDir -VariableType 'User'

$filename64 | Remove-Item -Force -ErrorAction SilentlyContinue
Write-Host "Software installed to '$destDir'"
Write-Host 'Build provided by TuxProject.de - consider donating to help support their server costs.'

tools\chocolateyUninstall.ps1

$ErrorActionPreference = 'Stop'

$toolsDir = Split-Path -parent $MyInvocation.MyCommand.Definition
$destDir = Join-Path -Path $toolsDir -ChildPath 'vim'

Get-ChildItem -Path "$destDir\*.bat" | ForEach-Object {
    Uninstall-BinFile -Name $_.BaseName -Path $_
}

Uninstall-ChocolateyEnvironmentVariable -VariableName 'VIM' -VariableType 'User'

tools\complete-x64.7z

md5: C021E2988DD093C86389C2DF499E75C7 | sha1: 252A964DC3127F56D2B948AD7FABAE0D378D0F20 | sha256: 235B33F269C48EC25D8252A7F73489CAB9B756718F4C6C0B8E9EEFB78AD42811 | sha512: 8F2E5C661AE6C10F8BFE10E561EF5F426E53A6BDC65213D98186451A3227C26730D244129722863F0C087FEE2D218533472B38EB0814C32D027AC952BC244B0D

tools\LICENSE.txt

VIM LICENSE

I)  There are no restrictions on distributing unmodified copies of Vim except
    that they must include this license text.  You can also distribute
    unmodified parts of Vim, likewise unrestricted except that they must
    include this license text.  You are also allowed to include executables
    that you made from the unmodified Vim sources, plus your own usage
    examples and Vim scripts.

II) It is allowed to distribute a modified (or extended) version of Vim,
    including executables and/or source code, when the following four
    conditions are met:
    1) This license text must be included unmodified.
    2) The modified Vim must be distributed in one of the following five ways:
       a) If you make changes to Vim yourself, you must clearly describe in
          the distribution how to contact you.  When the maintainer asks you
          (in any way) for a copy of the modified Vim you distributed, you
          must make your changes, including source code, available to the
          maintainer without fee.  The maintainer reserves the right to
          include your changes in the official version of Vim.  What the
          maintainer will do with your changes and under what license they
          will be distributed is negotiable.  If there has been no negotiation
          then this license, or a later version, also applies to your changes.
          The current maintainers are listed here: https://github.com/orgs/vim/people.
          If this changes it will be announced in appropriate places (most likely
          vim.sf.net, www.vim.org and/or comp.editors). When it is completely
          impossible to contact the maintainer, the obligation to send him
          your changes ceases.  Once the maintainer has confirmed that he has
          received your changes they will not have to be sent again.
       b) If you have received a modified Vim that was distributed as
          mentioned under a) you are allowed to further distribute it
          unmodified, as mentioned at I).  If you make additional changes the
          text under a) applies to those changes.
       c) Provide all the changes, including source code, with every copy of
          the modified Vim you distribute.  This may be done in the form of a
          context diff.  You can choose what license to use for new code you
          add.  The changes and their license must not restrict others from
          making their own changes to the official version of Vim.
       d) When you have a modified Vim which includes changes as mentioned
          under c), you can distribute it without the source code for the
          changes if the following three conditions are met:
          - The license that applies to the changes permits you to distribute
            the changes to the Vim maintainer without fee or restriction, and
            permits the Vim maintainer to include the changes in the official
            version of Vim without fee or restriction.
          - You keep the changes for at least three years after last
            distributing the corresponding modified Vim.  When the maintainer
            or someone who you distributed the modified Vim to asks you (in
            any way) for the changes within this period, you must make them
            available to him.
          - You clearly describe in the distribution how to contact you.  This
            contact information must remain valid for at least three years
            after last distributing the corresponding modified Vim, or as long
            as possible.
       e) When the GNU General Public License (GPL) applies to the changes,
          you can distribute the modified Vim under the GNU GPL version 2 or
          any later version.
    3) A message must be added, at least in the output of the ":version"
       command and in the intro screen, such that the user of the modified Vim
       is able to see that it was modified.  When distributing as mentioned
       under 2)e) adding the message is only required for as far as this does
       not conflict with the license used for the changes.
    4) The contact information as required under 2)a) and 2)d) must not be
       removed or changed, except that the person himself can make
       corrections.

III) If you distribute a modified version of Vim, you are encouraged to use
     the Vim license for your changes and make them available to the
     maintainer, including the source code.  The preferred way to do this is
     by e-mail or by uploading the files to a server and e-mailing the URL.
     If the number of changes is small (e.g., a modified Makefile) e-mailing a
     context diff will do.  The e-mail address to be used is
     <[email protected]>

IV)  It is not allowed to remove this license from the distribution of the Vim
     sources, parts of it or from a modified version.  You may use this
     license for previous Vim releases instead of the license that they came
     with, at your option.

tools\VERIFICATION.txt

VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

The embedded software have been downloaded from the listed download
location on <https://tuxproject.de/projects/vim/>
and can be verified by doing the following:

1. Download the following installers:
  32-Bit: <http://tuxproject.de/projects/vim/complete-x86.7z>
  64-Bit: <http://tuxproject.de/projects/vim/complete-x64.7z>

2. Get the checksum using one of the following methods:
  - Using PowerShell function 'Get-FileHash'
  - Use chocolatey utility 'checksum.exe'

3. The checksums should match the following:
    - complete-x64.7z: 235B33F269C48EC25D8252A7F73489CAB9B756718F4C6C0B8E9EEFB78AD42811 (SHA256)

    The files in the vim90 folder are taken from C:\Windows after a default
    installation of vim-tux (or the vim-tux.install package).

The file 'LICENSE.txt' has been obtained from https://github.com/vim/vim/blob/master/LICENSE

Virus Scan Results

No results available for this package. We are building up results for older packages over time so expect to see results. If this is a new package, it should have results within a day or two.

Version History

Version	Downloads	Last Updated	Status
Vim Tux (Portable) 9.1.1129	9	Friday, February 21, 2025	Approved
Vim Tux (Portable) 9.1.1122	12	Thursday, February 20, 2025	Approved
Vim Tux (Portable) 9.1.1119	10	Tuesday, February 18, 2025	Approved
Vim Tux (Portable) 9.1.1117	12	Monday, February 17, 2025	Approved
Vim Tux (Portable) 9.1.1106	10	Thursday, February 13, 2025	Approved
Vim Tux (Portable) 9.1.1076	5	Wednesday, February 5, 2025	Waiting for Maintainer
Vim Tux (Portable) 9.1.1074	8	Tuesday, February 4, 2025	Waiting for Maintainer
Vim Tux (Portable) 9.1.1071	24	Monday, February 3, 2025	Approved
Vim Tux (Portable) 9.1.1057	8	Friday, January 31, 2025	Waiting for Maintainer
Vim Tux (Portable) 9.1.1056	18	Thursday, January 30, 2025	Approved
Vim Tux (Portable) 9.1.1054	9	Tuesday, January 28, 2025	Waiting for Maintainer
Vim Tux (Portable) 9.1.1046	43	Thursday, January 23, 2025	Approved
Vim Tux (Portable) 9.1.1043	26	Wednesday, January 22, 2025	Approved
Vim Tux (Portable) 9.1.1039	25	Tuesday, January 21, 2025	Approved
Vim Tux (Portable) 9.1.1012	32	Monday, January 13, 2025	Approved
Vim Tux (Portable) 9.1.1000	30	Friday, January 10, 2025	Approved
Vim Tux (Portable) 9.1.998	27	Thursday, January 9, 2025	Approved
Vim Tux (Portable) 9.1.990	31	Tuesday, January 7, 2025	Approved
Vim Tux (Portable) 9.1.980	32	Monday, December 30, 2024	Approved
Vim Tux (Portable) 9.1.942	31	Wednesday, December 18, 2024	Approved
Vim Tux (Portable) 9.1.923	33	Saturday, December 14, 2024	Approved
Vim Tux (Portable) 9.1.899	41	Monday, December 2, 2024	Approved
Vim Tux (Portable) 9.1.892	31	Friday, November 29, 2024	Approved
Vim Tux (Portable) 9.1.888	36	Tuesday, November 26, 2024	Approved
Vim Tux (Portable) 9.1.861	44	Wednesday, November 13, 2024	Approved
Vim Tux (Portable) 9.1.849	35	Monday, November 11, 2024	Approved
Vim Tux (Portable) 9.1.847	49	Friday, November 8, 2024	Approved
Vim Tux (Portable) 9.1.837	34	Monday, November 4, 2024	Approved
Vim Tux (Portable) 9.1.818	39	Monday, October 28, 2024	Approved
Vim Tux (Portable) 9.1.813	37	Thursday, October 24, 2024	Approved
Vim Tux (Portable) 9.1.810	31	Thursday, October 24, 2024	Approved
Vim Tux (Portable) 9.1.792	42	Saturday, October 19, 2024	Approved
Vim Tux (Portable) 9.1.785	42	Tuesday, October 15, 2024	Approved
Vim Tux (Portable) 9.1.766	42	Wednesday, October 9, 2024	Approved
Vim Tux (Portable) 9.1.758	54	Saturday, October 5, 2024	Approved
Vim Tux (Portable) 9.1.757	42	Friday, October 4, 2024	Approved
Vim Tux (Portable) 9.1.736	53	Wednesday, September 18, 2024	Approved
Vim Tux (Portable) 9.1.730	61	Saturday, September 14, 2024	Approved
Vim Tux (Portable) 9.1.724	44	Wednesday, September 11, 2024	Approved
Vim Tux (Portable) 9.1.722	49	Tuesday, September 10, 2024	Approved
Vim Tux (Portable) 9.1.718	54	Friday, September 6, 2024	Approved
Vim Tux (Portable) 9.1.714	49	Thursday, September 5, 2024	Approved
Vim Tux (Portable) 9.1.708	55	Monday, September 2, 2024	Approved
Vim Tux (Portable) 9.1.697	72	Monday, August 26, 2024	Approved
Vim Tux (Portable) 9.1.689	53	Friday, August 23, 2024	Approved
Vim Tux (Portable) 9.1.685	51	Wednesday, August 21, 2024	Approved
Vim Tux (Portable) 9.1.682	38	Tuesday, August 20, 2024	Approved
Vim Tux (Portable) 9.1.675	47	Friday, August 16, 2024	Approved
Vim Tux (Portable) 9.1.668	60	Saturday, August 10, 2024	Approved
Vim Tux (Portable) 9.1.661	63	Tuesday, August 6, 2024	Approved
Vim Tux (Portable) 9.1.660	40	Monday, August 5, 2024	Approved
Vim Tux (Portable) 9.1.645	72	Thursday, August 1, 2024	Approved
Vim Tux (Portable) 9.1.643	52	Wednesday, July 31, 2024	Approved
Vim Tux (Portable) 9.1.636	61	Tuesday, July 30, 2024	Approved
Vim Tux (Portable) 9.1.608	71	Monday, July 22, 2024	Approved
Vim Tux (Portable) 9.1.602	65	Friday, July 19, 2024	Approved
Vim Tux (Portable) 9.1.598	59	Friday, July 19, 2024	Approved
Vim Tux (Portable) 9.1.586	58	Tuesday, July 16, 2024	Approved
Vim Tux (Portable) 9.1.571	54	Friday, July 12, 2024	Approved
Vim Tux (Portable) 9.1.554	65	Thursday, July 11, 2024	Approved
Vim Tux (Portable) 9.1.546	47	Tuesday, July 9, 2024	Approved
Vim Tux (Portable) 9.1.544	55	Tuesday, July 9, 2024	Approved
Vim Tux (Portable) 9.1.531	51	Saturday, July 6, 2024	Approved
Vim Tux (Portable) 9.1.516	71	Monday, June 24, 2024	Approved
Vim Tux (Portable) 9.1.514	64	Saturday, June 22, 2024	Approved
Vim Tux (Portable) 9.1.505	49	Thursday, June 20, 2024	Approved
Vim Tux (Portable) 9.1.500	53	Wednesday, June 19, 2024	Approved
Vim Tux (Portable) 9.1.496	60	Tuesday, June 18, 2024	Approved
Vim Tux (Portable) 9.1.491	62	Saturday, June 15, 2024	Approved
Vim Tux (Portable) 9.1.487	63	Saturday, June 15, 2024	Approved
Vim Tux (Portable) 9.1.478	56	Thursday, June 13, 2024	Approved
Vim Tux (Portable) 9.1.474	51	Tuesday, June 11, 2024	Approved
Vim Tux (Portable) 9.1.472	55	Monday, June 10, 2024	Approved
Vim Tux (Portable) 9.1.470	57	Thursday, June 6, 2024	Approved
Vim Tux (Portable) 9.1.466	62	Thursday, June 6, 2024	Approved
Vim Tux (Portable) 9.1.461	57	Tuesday, June 4, 2024	Approved
Vim Tux (Portable) 9.1.454	66	Saturday, June 1, 2024	Approved
Vim Tux (Portable) 9.1.448	60	Thursday, May 30, 2024	Approved
Vim Tux (Portable) 9.1.447	67	Tuesday, May 28, 2024	Approved
Vim Tux (Portable) 9.1.442	64	Saturday, May 25, 2024	Approved
Vim Tux (Portable) 9.1.433	49	Friday, May 24, 2024	Approved
Vim Tux (Portable) 9.1.432	62	Thursday, May 23, 2024	Approved
Vim Tux (Portable) 9.1.426	65	Wednesday, May 22, 2024	Approved
Vim Tux (Portable) 9.1.412	80	Tuesday, May 21, 2024	Approved
Vim Tux (Portable) 9.1.411	49	Monday, May 13, 2024	Approved
Vim Tux (Portable) 9.1.407	60	Sunday, May 12, 2024	Approved
Vim Tux (Portable) 9.1.393	58	Wednesday, May 8, 2024	Approved
Vim Tux (Portable) 9.1.386	66	Thursday, May 2, 2024	Approved
Vim Tux (Portable) 9.1.380	71	Tuesday, April 30, 2024	Approved
Vim Tux (Portable) 9.1.369	68	Thursday, April 25, 2024	Approved
Vim Tux (Portable) 9.1.368	58	Thursday, April 25, 2024	Approved
Vim Tux (Portable) 9.1.366	63	Tuesday, April 23, 2024	Approved
Vim Tux (Portable) 9.1.363	64	Monday, April 22, 2024	Approved
Vim Tux (Portable) 9.1.354	56	Saturday, April 20, 2024	Approved
Vim Tux (Portable) 9.1.336	64	Tuesday, April 16, 2024	Approved
Vim Tux (Portable) 9.1.330	67	Monday, April 15, 2024	Approved
Vim Tux (Portable) 9.1.296	68	Thursday, April 11, 2024	Approved
Vim Tux (Portable) 9.1.193	80	Friday, March 22, 2024	Approved
Vim Tux (Portable) 9.1.186	75	Tuesday, March 19, 2024	Approved
Vim Tux (Portable) 9.1.181	64	Saturday, March 16, 2024	Approved
Vim Tux (Portable) 9.1.149	76	Tuesday, March 5, 2024	Approved
Vim Tux (Portable) 9.1.113	85	Friday, February 16, 2024	Approved
Vim Tux (Portable) 9.1.67	81	Friday, February 2, 2024	Approved
Vim Tux (Portable) 9.1.50	71	Tuesday, January 30, 2024	Approved
Vim Tux (Portable) 9.0.2181	118	Thursday, December 21, 2023	Approved
Vim Tux (Portable) 9.0.2167	76	Friday, December 15, 2023	Approved
Vim Tux (Portable) 9.0.2155	79	Saturday, December 9, 2023	Approved
Vim Tux (Portable) 9.0.2122	82	Friday, November 24, 2023	Approved
Vim Tux (Portable) 9.0.2120	76	Thursday, November 23, 2023	Approved
Vim Tux (Portable) 9.0.2105	78	Wednesday, November 15, 2023	Approved
Vim Tux (Portable) 9.0.2103	90	Tuesday, November 14, 2023	Approved
Vim Tux (Portable) 9.0.2095	78	Thursday, November 9, 2023	Approved
Vim Tux (Portable) 9.0.2092	73	Tuesday, November 7, 2023	Approved
Vim Tux (Portable) 9.0.2081	95	Wednesday, November 1, 2023	Approved
Vim Tux (Portable) 9.0.2077	83	Saturday, October 28, 2023	Approved
Vim Tux (Portable) 9.0.2063	275	Tuesday, October 24, 2023	Approved
Vim Tux (Portable) 9.0.2053	88	Friday, October 20, 2023	Approved
Vim Tux (Portable) 9.0.2050	78	Thursday, October 19, 2023	Approved
Vim Tux (Portable) 9.0.2048	87	Thursday, October 19, 2023	Approved
Vim Tux (Portable) 9.0.2043	71	Wednesday, October 18, 2023	Approved
Vim Tux (Portable) 9.0.2034	85	Tuesday, October 17, 2023	Approved
Vim Tux (Portable) 9.0.2009	75	Tuesday, October 10, 2023	Approved
Vim Tux (Portable) 9.0.1976	73	Wednesday, October 4, 2023	Approved
Vim Tux (Portable) 9.0.1943	70	Wednesday, September 27, 2023	Approved
Vim Tux (Portable) 9.0.1927	559	Thursday, September 21, 2023	Approved
Vim Tux (Portable) 9.0.1907	868	Monday, September 18, 2023	Approved
Vim Tux (Portable) 9.0.1901	637	Sunday, September 17, 2023	Approved
Vim Tux (Portable) 9.0.1897	117	Wednesday, September 13, 2023	Approved
Vim Tux (Portable) 9.0.1877	109	Friday, September 8, 2023	Exempted
Vim Tux (Portable) 9.0.1811	80	Monday, August 28, 2023	Exempted
Vim Tux (Portable) 9.0.1787	70	Monday, August 28, 2023	Approved
Vim Tux (Portable) 9.0.0846	278	Thursday, November 10, 2022	Approved
Vim Tux (Portable) 9.0.0828	102	Friday, November 4, 2022	Approved
Vim Tux (Portable) 9.0.0815	107	Wednesday, October 26, 2022	Approved
Vim Tux (Portable) 9.0.0814	91	Saturday, October 22, 2022	Approved
Vim Tux (Portable) 9.0.0806	102	Friday, October 21, 2022	Approved
Vim Tux (Portable) 9.0.0797	84	Thursday, October 20, 2022	Approved
Vim Tux (Portable) 9.0.0780	104	Tuesday, October 18, 2022	Approved
Vim Tux (Portable) 9.0.0733	112	Thursday, October 13, 2022	Approved
Vim Tux (Portable) 9.0.0715	113	Tuesday, October 11, 2022	Approved
Vim Tux (Portable) 9.0.0682	99	Saturday, October 8, 2022	Approved
Vim Tux (Portable) 9.0.656.20221005	116	Thursday, October 6, 2022	Approved
Vim Tux (Portable) 9.0.0656	103	Wednesday, October 5, 2022	Approved
Vim Tux (Portable) 8.2.3908	325	Monday, December 27, 2021	Approved
Vim Tux (Portable) 8.2.3875	117	Thursday, December 23, 2021	Approved
Vim Tux (Portable) 8.2.3858	137	Tuesday, December 21, 2021	Approved
Vim Tux (Portable) 8.2.3836	131	Saturday, December 18, 2021	Approved
Vim Tux (Portable) 8.2.3811	136	Wednesday, December 15, 2021	Approved
Vim Tux (Portable) 8.2.3794	121	Tuesday, December 14, 2021	Approved
Vim Tux (Portable) 8.2.3763	134	Friday, December 10, 2021	Approved
Vim Tux (Portable) 8.2.3757	114	Wednesday, December 8, 2021	Approved
Vim Tux (Portable) 8.2.3752	123	Tuesday, December 7, 2021	Approved
Vim Tux (Portable) 8.2.3718	134	Friday, December 3, 2021	Approved
Vim Tux (Portable) 8.2.3717	139	Thursday, December 2, 2021	Approved
Vim Tux (Portable) 8.2.3701	119	Tuesday, November 30, 2021	Approved
Vim Tux (Portable) 8.2.3692	118	Monday, November 29, 2021	Approved
Vim Tux (Portable) 8.2.3671	146	Friday, November 26, 2021	Approved
Vim Tux (Portable) 8.2.3659	127	Thursday, November 25, 2021	Approved
Vim Tux (Portable) 8.2.3651	133	Tuesday, November 23, 2021	Approved
Vim Tux (Portable) 8.2.3646	112	Tuesday, November 23, 2021	Approved
Vim Tux (Portable) 8.2.3623	124	Saturday, November 20, 2021	Approved
Vim Tux (Portable) 8.2.3608	134	Thursday, November 18, 2021	Approved
Vim Tux (Portable) 8.2.3595	116	Tuesday, November 16, 2021	Approved
Vim Tux (Portable) 8.2.3579	149	Friday, November 5, 2021	Approved
Vim Tux (Portable) 8.2.3565	128	Wednesday, October 27, 2021	Approved
Vim Tux (Portable) 8.2.3551	122	Friday, October 22, 2021	Approved
Vim Tux (Portable) 8.2.3545	117	Thursday, October 21, 2021	Approved
Vim Tux (Portable) 8.2.3532	119	Tuesday, October 19, 2021	Approved
Vim Tux (Portable) 8.2.3513	142	Saturday, October 16, 2021	Approved
Vim Tux (Portable) 8.2.3505	117	Thursday, October 14, 2021	Approved
Vim Tux (Portable) 8.2.3493	129	Tuesday, October 12, 2021	Approved
Vim Tux (Portable) 8.2.3486	110	Saturday, October 9, 2021	Approved
Vim Tux (Portable) 8.2.3484	119	Thursday, October 7, 2021	Approved
Vim Tux (Portable) 8.2.3478	122	Wednesday, October 6, 2021	Approved
Vim Tux (Portable) 8.2.3469	127	Tuesday, October 5, 2021	Approved
Vim Tux (Portable) 8.2.3458	125	Tuesday, September 28, 2021	Approved
Vim Tux (Portable) 8.2.3455	116	Thursday, September 23, 2021	Approved
Vim Tux (Portable) 8.2.3450	133	Tuesday, September 21, 2021	Approved
Vim Tux (Portable) 8.2.3448	129	Sunday, September 19, 2021	Approved
Vim Tux (Portable) 8.2.3434	138	Tuesday, September 14, 2021	Approved
Vim Tux (Portable) 8.2.3416	137	Thursday, September 9, 2021	Approved
Vim Tux (Portable) 8.2.3394	129	Thursday, September 2, 2021	Approved
Vim Tux (Portable) 8.2.3391	145	Wednesday, September 1, 2021	Approved
Vim Tux (Portable) 8.2.3376	160	Friday, August 27, 2021	Approved
Vim Tux (Portable) 8.2.3358	142	Friday, August 20, 2021	Approved
Vim Tux (Portable) 8.2.3356	123	Wednesday, August 18, 2021	Approved
Vim Tux (Portable) 8.2.3326	182	Wednesday, August 11, 2021	Approved
Vim Tux (Portable) 8.2.3318	143	Monday, August 9, 2021	Approved
Vim Tux (Portable) 8.2.3299	133	Friday, August 6, 2021	Approved
Vim Tux (Portable) 8.2.3290	113	Thursday, August 5, 2021	Approved
Vim Tux (Portable) 8.2.3281	138	Wednesday, August 4, 2021	Approved
Vim Tux (Portable) 8.2.3273	140	Tuesday, August 3, 2021	Approved
Vim Tux (Portable) 8.2.3269	140	Monday, August 2, 2021	Approved
Vim Tux (Portable) 8.2.3263	119	Sunday, August 1, 2021	Approved
Vim Tux (Portable) 8.2.3253	146	Saturday, July 31, 2021	Approved
Vim Tux (Portable) 8.2.3242	127	Thursday, July 29, 2021	Approved
Vim Tux (Portable) 8.2.3223	124	Tuesday, July 27, 2021	Approved
Vim Tux (Portable) 8.2.3204	126	Friday, July 23, 2021	Approved
Vim Tux (Portable) 8.2.3187	131	Tuesday, July 20, 2021	Approved
Vim Tux (Portable) 8.2.3171	144	Friday, July 16, 2021	Approved
Vim Tux (Portable) 8.2.3158	163	Wednesday, July 14, 2021	Approved
Vim Tux (Portable) 8.2.3131	128	Friday, July 9, 2021	Approved
Vim Tux (Portable) 8.2.3120	140	Thursday, July 8, 2021	Approved
Vim Tux (Portable) 8.2.3113	136	Wednesday, July 7, 2021	Approved
Vim Tux (Portable) 8.2.3107	130	Tuesday, July 6, 2021	Approved
Vim Tux (Portable) 8.2.3104	129	Monday, July 5, 2021	Approved
Vim Tux (Portable) 8.2.3095	137	Sunday, July 4, 2021	Approved
Vim Tux (Portable) 8.2.3080	133	Thursday, July 1, 2021	Approved
Vim Tux (Portable) 8.2.3075	129	Wednesday, June 30, 2021	Approved
Vim Tux (Portable) 8.2.3066	142	Monday, June 28, 2021	Approved
Vim Tux (Portable) 8.2.3055	127	Sunday, June 27, 2021	Approved
Vim Tux (Portable) 8.2.3043	136	Thursday, June 24, 2021	Approved
Vim Tux (Portable) 8.2.3033	127	Tuesday, June 22, 2021	Approved
Vim Tux (Portable) 8.2.3020	118	Sunday, June 20, 2021	Approved
Vim Tux (Portable) 8.2.3017	141	Friday, June 18, 2021	Approved
Vim Tux (Portable) 8.2.2840	185	Saturday, May 8, 2021	Approved
Vim Tux (Portable) 8.2.2832	154	Wednesday, May 5, 2021	Approved
Vim Tux (Portable) 8.2.2815	185	Wednesday, April 28, 2021	Approved
Vim Tux (Portable) 8.2.2799	192	Thursday, April 22, 2021	Approved
Vim Tux (Portable) 8.2.2794	142	Wednesday, April 21, 2021	Approved
Vim Tux (Portable) 8.2.2763	145	Thursday, April 15, 2021	Approved
Vim Tux (Portable) 8.2.2738	151	Friday, April 9, 2021	Approved
Vim Tux (Portable) 8.2.2730	174	Wednesday, April 7, 2021	Approved
Vim Tux (Portable) 8.2.2679	145	Wednesday, March 31, 2021	Approved
Vim Tux (Portable) 8.2.2650	141	Friday, March 26, 2021	Approved
Vim Tux (Portable) 8.2.2648	163	Wednesday, March 24, 2021	Approved
Vim Tux (Portable) 8.2.2637	138	Tuesday, March 23, 2021	Approved
Vim Tux (Portable) 8.2.2491	222	Thursday, February 11, 2021	Approved
Vim Tux (Portable) 8.2.2129	231	Saturday, December 12, 2020	Approved
Vim Tux (Portable) 8.2.1981	178	Saturday, November 14, 2020	Approved
Vim Tux (Portable) 8.2.1955	188	Friday, November 6, 2020	Approved
Vim Tux (Portable) 8.2.1923	193	Friday, October 30, 2020	Approved
Vim Tux (Portable) 8.2.1883	188	Thursday, October 22, 2020	Approved
Vim Tux (Portable) 8.2.1858	171	Sunday, October 18, 2020	Approved
Vim Tux (Portable) 8.2.1738	224	Friday, September 25, 2020	Approved
Vim Tux (Portable) 8.2.1651	210	Thursday, September 10, 2020	Approved
Vim Tux (Portable) 8.2.1058	277	Friday, June 26, 2020	Approved
Vim Tux (Portable) 8.2.1007	201	Friday, June 19, 2020	Approved
Vim Tux (Portable) 8.2.988	247	Wednesday, June 17, 2020	Approved
Vim Tux (Portable) 8.2.960	210	Friday, June 12, 2020	Approved
Vim Tux (Portable) 8.2.950	200	Thursday, June 11, 2020	Approved
Vim Tux (Portable) 8.2.916	221	Sunday, June 7, 2020	Approved
Vim Tux (Portable) 8.2.882	211	Tuesday, June 2, 2020	Approved
Vim Tux (Portable) 8.2.855	197	Sunday, May 31, 2020	Approved
Vim Tux (Portable) 8.2.834	229	Friday, May 29, 2020	Approved
Vim Tux (Portable) 8.2.829	238	Wednesday, May 27, 2020	Approved
Vim Tux (Portable) 8.2.821	189	Tuesday, May 26, 2020	Approved
Vim Tux (Portable) 8.2.806	206	Friday, May 22, 2020	Approved
Vim Tux (Portable) 8.2.803	193	Thursday, May 21, 2020	Approved
Vim Tux (Portable) 8.2.766	230	Sunday, May 17, 2020	Approved
Vim Tux (Portable) 8.2.750	220	Thursday, May 14, 2020	Approved
Vim Tux (Portable) 8.2.735	227	Tuesday, May 12, 2020	Approved
Vim Tux (Portable) 8.2.647	267	Monday, April 27, 2020	Approved
Vim Tux (Portable) 8.2.640	187	Sunday, April 26, 2020	Approved
Vim Tux (Portable) 8.2.625	203	Friday, April 24, 2020	Approved
Vim Tux (Portable) 8.2.612	272	Tuesday, April 21, 2020	Approved
Vim Tux (Portable) 8.2.592	219	Saturday, April 18, 2020	Approved
Vim Tux (Portable) 8.2.585	189	Friday, April 17, 2020	Approved
Vim Tux (Portable) 8.2.577	234	Tuesday, April 14, 2020	Approved
Vim Tux (Portable) 8.2.0536	220	Sunday, April 12, 2020	Approved
Vim Tux (Portable) 8.2.0515	236	Monday, April 6, 2020	Approved
Vim Tux (Portable) 8.2.0505	224	Saturday, April 4, 2020	Approved
Vim Tux (Portable) 8.2.0486	205	Wednesday, April 1, 2020	Approved
Vim Tux (Portable) 8.2.0464	227	Sunday, March 29, 2020	Approved
Vim Tux (Portable) 8.2.0397	240	Wednesday, March 18, 2020	Approved
Vim Tux (Portable) 8.2.0369	252	Wednesday, March 11, 2020	Approved
Vim Tux (Portable) 8.2.0357	244	Friday, March 6, 2020	Approved
Vim Tux (Portable) 8.2.0324	240	Friday, February 28, 2020	Approved
Vim Tux (Portable) 8.2.0313	220	Monday, February 24, 2020	Approved
Vim Tux (Portable) 8.2.0294	208	Saturday, February 22, 2020	Approved
Vim Tux (Portable) 8.2.0285	191	Friday, February 21, 2020	Approved
Vim Tux (Portable) 8.2.0273	224	Tuesday, February 18, 2020	Approved
Vim Tux (Portable) 8.2.0231	259	Sunday, February 9, 2020	Approved
Vim Tux (Portable) 8.2.0164	241	Wednesday, January 29, 2020	Approved
Vim Tux (Portable) 8.2.0147	184	Saturday, January 25, 2020	Approved
Vim Tux (Portable) 8.2.0129	252	Sunday, January 19, 2020	Approved
Vim Tux (Portable) 8.2.0114	217	Tuesday, January 14, 2020	Approved
Vim Tux (Portable) 8.2.0109	204	Friday, January 10, 2020	Approved
Vim Tux (Portable) 8.2.0092	230	Tuesday, January 7, 2020	Approved
Vim Tux (Portable) 8.2.0080	238	Friday, January 3, 2020	Approved
Vim Tux (Portable) 8.2.0065	232	Tuesday, December 31, 2019	Approved
Vim Tux (Portable) 8.2.0055	200	Monday, December 30, 2019	Approved
Vim Tux (Portable) 8.2.0052	216	Sunday, December 29, 2019	Approved
Vim Tux (Portable) 8.2.0033	213	Tuesday, December 24, 2019	Approved
Vim Tux (Portable) 8.2.0021	201	Thursday, December 19, 2019	Approved
Vim Tux (Portable) 8.2.0011	218	Monday, December 16, 2019	Approved
Vim Tux (Portable) 8.1.2333	286	Friday, November 22, 2019	Approved
Vim Tux (Portable) 8.1.2323	275	Thursday, November 21, 2019	Approved
Vim Tux (Portable) 8.1.2311	260	Sunday, November 17, 2019	Approved
Vim Tux (Portable) 8.1.2300	223	Thursday, November 14, 2019	Approved
Vim Tux (Portable) 8.1.2237	257	Friday, November 1, 2019	Approved
Vim Tux (Portable) 8.1.2204	304	Thursday, October 24, 2019	Approved
Vim Tux (Portable) 8.1.2200	244	Wednesday, October 23, 2019	Approved
Vim Tux (Portable) 8.1.2148	261	Monday, October 14, 2019	Approved
Vim Tux (Portable) 8.1.2133	220	Friday, October 11, 2019	Approved
Vim Tux (Portable) 8.1.2117	250	Sunday, October 6, 2019	Approved
Vim Tux (Portable) 8.1.2108	256	Thursday, October 3, 2019	Approved
Vim Tux (Portable) 8.1.2103	205	Tuesday, October 1, 2019	Approved
Vim Tux (Portable) 8.1.2079	267	Friday, September 27, 2019	Approved
Vim Tux (Portable) 8.1.2071	200	Wednesday, September 25, 2019	Approved
Vim Tux (Portable) 8.1.2052	229	Thursday, September 19, 2019	Approved
Vim Tux (Portable) 8.1.2019	278	Tuesday, September 10, 2019	Approved
Vim Tux (Portable) 8.1.2004	242	Sunday, September 8, 2019	Approved
Vim Tux (Portable) 8.1.1995	219	Saturday, September 7, 2019	Approved
Vim Tux (Portable) 8.1.1986	234	Thursday, September 5, 2019	Approved
Vim Tux (Portable) 8.1.1961	234	Monday, September 2, 2019	Approved
Vim Tux (Portable) 8.1.1927	272	Monday, August 26, 2019	Approved
Vim Tux (Portable) 8.1.1915	228	Saturday, August 24, 2019	Approved
Vim Tux (Portable) 8.1.1906	247	Thursday, August 22, 2019	Approved
Vim Tux (Portable) 8.1.1890	210	Tuesday, August 20, 2019	Approved
Vim Tux (Portable) 8.1.1836	278	Sunday, August 11, 2019	Approved
Vim Tux (Portable) 8.1.1813	270	Monday, August 5, 2019	Approved
Vim Tux (Portable) 8.1.1744	234	Thursday, July 25, 2019	Approved
Vim Tux (Portable) 8.1.1729	238	Tuesday, July 23, 2019	Approved
Vim Tux (Portable) 8.1.1713	245	Friday, July 19, 2019	Approved
Vim Tux (Portable) 8.1.1695	240	Tuesday, July 16, 2019	Approved
Vim Tux (Portable) 8.1.1669	227	Saturday, July 13, 2019	Approved
Vim Tux (Portable) 8.1.1655	276	Tuesday, July 9, 2019	Approved
Vim Tux (Portable) 8.1.1631	227	Friday, July 5, 2019	Approved
Vim Tux (Portable) 8.1.1601	287	Thursday, June 27, 2019	Approved
Vim Tux (Portable) 8.1.1578	243	Saturday, June 22, 2019	Approved
Vim Tux (Portable) 8.1.1573	271	Thursday, June 20, 2019	Approved
Vim Tux (Portable) 8.1.1566	218	Tuesday, June 18, 2019	Approved
Vim Tux (Portable) 8.1.1557	256	Monday, June 17, 2019	Approved
Vim Tux (Portable) 8.1.1536	206	Sunday, June 16, 2019	Approved
Vim Tux (Portable) 8.1.1523	248	Friday, June 14, 2019	Approved
Vim Tux (Portable) 8.1.1515	257	Tuesday, June 11, 2019	Approved
Vim Tux (Portable) 8.1.1511	252	Monday, June 10, 2019	Approved
Vim Tux (Portable) 8.1.1455	236	Monday, June 3, 2019	Approved
Vim Tux (Portable) 8.1.1432	282	Friday, May 31, 2019	Approved
Vim Tux (Portable) 8.1.1413	268	Tuesday, May 28, 2019	Approved
Vim Tux (Portable) 8.1.1373	282	Friday, May 24, 2019	Approved
Vim Tux (Portable) 8.1.1364	260	Thursday, May 23, 2019	Approved
Vim Tux (Portable) 8.1.1353	224	Monday, May 20, 2019	Approved
Vim Tux (Portable) 8.1.1333	261	Thursday, May 16, 2019	Approved
Vim Tux (Portable) 8.1.1328	228	Monday, May 13, 2019	Approved
Vim Tux (Portable) 8.1.1312	225	Saturday, May 11, 2019	Approved
Vim Tux (Portable) 8.1.1298	255	Thursday, May 9, 2019	Approved
Vim Tux (Portable) 8.1.1286	272	Tuesday, May 7, 2019	Approved
Vim Tux (Portable) 8.1.1197	281	Monday, April 22, 2019	Approved
Vim Tux (Portable) 8.1.1183	252	Thursday, April 18, 2019	Approved
Vim Tux (Portable) 8.1.1165	249	Sunday, April 14, 2019	Approved
Vim Tux (Portable) 8.1.1140	236	Tuesday, April 9, 2019	Approved
Vim Tux (Portable) 8.1.1136	236	Monday, April 8, 2019	Approved
Vim Tux (Portable) 8.1.1124	242	Sunday, April 7, 2019	Approved
Vim Tux (Portable) 8.1.1103	274	Thursday, April 4, 2019	Approved
Vim Tux (Portable) 8.1.1097	284	Monday, April 1, 2019	Approved
Vim Tux (Portable) 8.1.1073	208	Saturday, March 30, 2019	Approved
Vim Tux (Portable) 8.1.1057	280	Thursday, March 28, 2019	Approved
Vim Tux (Portable) 8.1.1032	290	Friday, March 22, 2019	Approved
Vim Tux (Portable) 8.1.1027	281	Thursday, March 21, 2019	Approved
Vim Tux (Portable) 8.1.1017	215	Tuesday, March 19, 2019	Approved
Vim Tux (Portable) 8.1.1004	247	Monday, March 11, 2019	Approved
Vim Tux (Portable) 8.1.998	236	Friday, March 8, 2019	Approved
Vim Tux (Portable) 8.1.990	277	Sunday, March 3, 2019	Approved
Vim Tux (Portable) 8.1.984	246	Thursday, February 28, 2019	Approved
Vim Tux (Portable) 8.1.978	251	Saturday, February 23, 2019	Approved
Vim Tux (Portable) 8.1.966	267	Friday, February 22, 2019	Approved
Vim Tux (Portable) 8.1.947	247	Tuesday, February 19, 2019	Approved
Vim Tux (Portable) 8.1.934	188	Sunday, February 17, 2019	Approved
Vim Tux (Portable) 8.1.926	259	Saturday, February 16, 2019	Approved
Vim Tux (Portable) 8.1.909	240	Thursday, February 14, 2019	Approved
Vim Tux (Portable) 8.1.895	251	Tuesday, February 12, 2019	Approved
Vim Tux (Portable) 8.1.0885	250	Sunday, February 10, 2019	Approved
Vim Tux (Portable) 8.1.0877	273	Thursday, February 7, 2019	Approved
Vim Tux (Portable) 8.1.0871	253	Monday, February 4, 2019	Approved
Vim Tux (Portable) 8.1.0868	274	Sunday, February 3, 2019	Approved
Vim Tux (Portable) 8.1.0865	223	Saturday, February 2, 2019	Approved
Vim Tux (Portable) 8.1.0842	257	Thursday, January 31, 2019	Approved
Vim Tux (Portable) 8.1.0837	281	Monday, January 28, 2019	Approved
Vim Tux (Portable) 8.1.0814	257	Friday, January 25, 2019	Approved
Vim Tux (Portable) 8.1.0796	249	Thursday, January 24, 2019	Approved
Vim Tux (Portable) 8.1.0788	253	Tuesday, January 22, 2019	Approved
Vim Tux (Portable) 8.1.0757	301	Thursday, January 17, 2019	Approved
Vim Tux (Portable) 8.1.0749	236	Tuesday, January 15, 2019	Approved
Vim Tux (Portable) 8.1.0727	231	Saturday, January 12, 2019	Approved
Vim Tux (Portable) 8.1.0712	297	Thursday, January 10, 2019	Approved
Vim Tux (Portable) 8.1.0700	247	Tuesday, January 8, 2019	Approved
Vim Tux (Portable) 8.1.0690	327	Saturday, January 5, 2019	Approved
Vim Tux (Portable) 8.1.0681	283	Thursday, January 3, 2019	Approved
Vim Tux (Portable) 8.1.0674	251	Wednesday, January 2, 2019	Approved
Vim Tux (Portable) 8.1.0647	294	Friday, December 28, 2018	Approved
Vim Tux (Portable) 8.1.0644	250	Thursday, December 27, 2018	Approved
Vim Tux (Portable) 8.1.0635	220	Wednesday, December 26, 2018	Approved
Vim Tux (Portable) 8.1.0630	256	Tuesday, December 25, 2018	Approved
Vim Tux (Portable) 8.1.0629	240	Monday, December 24, 2018	Approved
Vim Tux (Portable) 8.1.0622	238	Sunday, December 23, 2018	Approved
Vim Tux (Portable) 8.1.0617	264	Saturday, December 22, 2018	Approved
Vim Tux (Portable) 8.1.0594	246	Sunday, December 16, 2018	Approved
Vim Tux (Portable) 8.1.0577	261	Thursday, December 13, 2018	Approved
Vim Tux (Portable) 8.1.0551	281	Friday, November 30, 2018	Approved
Vim Tux (Portable) 8.1.0547	284	Monday, November 26, 2018	Approved
Vim Tux (Portable) 8.1.0536	273	Tuesday, November 20, 2018	Approved
Vim Tux (Portable) 8.1.0524	275	Tuesday, November 13, 2018	Approved
Vim Tux (Portable) 8.1.0513	281	Thursday, November 8, 2018	Approved
Vim Tux (Portable) 8.1.0509	266	Sunday, November 4, 2018	Approved
Vim Tux (Portable) 8.1.0498	245	Sunday, October 28, 2018	Approved
Vim Tux (Portable) 8.1.0489	299	Monday, October 22, 2018	Approved
Vim Tux (Portable) 8.1.0474	284	Monday, October 15, 2018	Approved
Vim Tux (Portable) 8.1.0470	280	Friday, October 12, 2018	Approved
Vim Tux (Portable) 8.1.0451	316	Friday, October 5, 2018	Approved
Vim Tux (Portable) 8.1.0442	274	Monday, October 1, 2018	Approved
Vim Tux (Portable) 8.1.0436	257	Thursday, September 27, 2018	Approved
Vim Tux (Portable) 8.1.0425	275	Saturday, September 22, 2018	Approved
Vim Tux (Portable) 8.1.0408	269	Thursday, September 20, 2018	Approved
Vim Tux (Portable) 8.1.0401	265	Tuesday, September 18, 2018	Approved
Vim Tux (Portable) 8.1.0385	298	Friday, September 14, 2018	Approved
Vim Tux (Portable) 8.1.0371	289	Thursday, September 13, 2018	Approved
Vim Tux (Portable) 8.1.0362	270	Tuesday, September 11, 2018	Approved
Vim Tux (Portable) 8.1.0354	290	Sunday, September 9, 2018	Approved
Vim Tux (Portable) 8.1.0347	265	Thursday, September 6, 2018	Approved
Vim Tux (Portable) 8.1.0342	263	Sunday, September 2, 2018	Approved
Vim Tux (Portable) 8.1.0332	275	Thursday, August 30, 2018	Approved
Vim Tux (Portable) 8.1.0327	263	Sunday, August 26, 2018	Approved
Vim Tux (Portable) 8.1.0318	266	Thursday, August 23, 2018	Approved
Vim Tux (Portable) 8.1.0301	264	Tuesday, August 21, 2018	Approved
Vim Tux (Portable) 8.1.0297	266	Monday, August 20, 2018	Approved
Vim Tux (Portable) 8.1.0288	294	Thursday, August 16, 2018	Approved
Vim Tux (Portable) 8.1.0278	278	Monday, August 13, 2018	Approved
Vim Tux (Portable) 8.1.0271	270	Sunday, August 12, 2018	Approved
Vim Tux (Portable) 8.1.0259	290	Friday, August 10, 2018	Approved
Vim Tux (Portable) 8.1.0239	311	Sunday, August 5, 2018	Approved
Vim Tux (Portable) 8.1.0229	295	Tuesday, July 31, 2018	Approved
Vim Tux (Portable) 8.1.0221	293	Sunday, July 29, 2018	Approved
Vim Tux (Portable) 8.1.0210	268	Thursday, July 26, 2018	Approved
Vim Tux (Portable) 8.1.0207	270	Tuesday, July 24, 2018	Approved
Vim Tux (Portable) 8.1.0203	293	Monday, July 23, 2018	Approved
Vim Tux (Portable) 8.1.0199	271	Saturday, July 21, 2018	Approved
Vim Tux (Portable) 8.1.0196	327	Friday, July 20, 2018	Approved
Vim Tux (Portable) 8.1.0191	263	Tuesday, July 17, 2018	Approved
Vim Tux (Portable) 8.1.0186	303	Sunday, July 15, 2018	Approved
Vim Tux (Portable) 8.1.0173	343	Tuesday, July 10, 2018	Approved
Vim Tux (Portable) 8.1.0153	320	Friday, July 6, 2018	Approved
Vim Tux (Portable) 8.1.0138	310	Tuesday, July 3, 2018	Approved
Vim Tux (Portable) 8.1.0133	269	Sunday, July 1, 2018	Approved
Vim Tux (Portable) 8.1.0126	298	Friday, June 29, 2018	Approved
Vim Tux (Portable) 8.1.0105	324	Sunday, June 24, 2018	Approved
Vim Tux (Portable) 8.1.0054	327	Thursday, June 14, 2018	Approved
Vim Tux (Portable) 8.1.0034	312	Tuesday, June 5, 2018	Approved
Vim Tux (Portable) 8.1.0022	335	Friday, May 25, 2018	Approved
Vim Tux (Portable) 8.1.0013	336	Tuesday, May 22, 2018	Approved
Vim Tux (Portable) 8.1.0009	303	Monday, May 21, 2018	Approved
Vim Tux (Portable) 8.1.0004	309	Sunday, May 20, 2018	Approved
Vim Tux (Portable) 8.1.0.20180519	331	Saturday, May 19, 2018	Approved
Vim Tux (Portable) 8.1.0000	315	Friday, May 18, 2018	Approved
Vim Tux (Portable) 8.0.1848	368	Thursday, May 17, 2018	Approved
Vim Tux (Portable) 8.0.1831	371	Monday, May 14, 2018	Approved
Vim Tux (Portable) 8.0.1820	335	Sunday, May 13, 2018	Approved
Vim Tux (Portable) 8.0.1806	360	Thursday, May 10, 2018	Approved
Vim Tux (Portable) 8.0.1799	313	Monday, May 7, 2018	Approved
Vim Tux (Portable) 8.0.1794	308	Sunday, May 6, 2018	Approved
Vim Tux (Portable) 8.0.1790	360	Friday, May 4, 2018	Approved
Vim Tux (Portable) 8.0.1788	322	Thursday, May 3, 2018	Approved
Vim Tux (Portable) 8.0.1774	381	Monday, April 30, 2018	Approved
Vim Tux (Portable) 8.0.1765	348	Thursday, April 26, 2018	Approved
Vim Tux (Portable) 8.0.1748	318	Sunday, April 22, 2018	Approved
Vim Tux (Portable) 8.0.1736	345	Friday, April 20, 2018	Approved
Vim Tux (Portable) 8.0.1727	328	Wednesday, April 18, 2018	Approved
Vim Tux (Portable) 8.0.1705	340	Saturday, April 14, 2018	Approved
Vim Tux (Portable) 8.0.1679	349	Monday, April 9, 2018	Approved
Vim Tux (Portable) 8.0.1664	314	Saturday, April 7, 2018	Approved
Vim Tux (Portable) 8.0.1655	334	Saturday, March 31, 2018	Approved
Vim Tux (Portable) 8.0.1638	368	Sunday, March 25, 2018	Approved
Vim Tux (Portable) 8.0.1626	436	Thursday, March 22, 2018	Approved
Vim Tux (Portable) 8.0.1612	351	Saturday, March 17, 2018	Approved
Vim Tux (Portable) 8.0.1601	357	Tuesday, March 13, 2018	Approved
Vim Tux (Portable) 8.0.1591	388	Friday, March 9, 2018	Approved
Vim Tux (Portable) 8.0.1563	361	Sunday, March 4, 2018	Approved
Vim Tux (Portable) 8.0.1553	367	Friday, March 2, 2018	Approved
Vim Tux (Portable) 8.0.1532	389	Sunday, February 25, 2018	Approved
Vim Tux (Portable) 8.0.1504	380	Thursday, February 15, 2018	Approved
Vim Tux (Portable) 8.0.1473	350	Thursday, February 8, 2018	Approved
Vim Tux (Portable) 8.0.1451	372	Saturday, February 3, 2018	Approved
Vim Tux (Portable) 8.0.1438	402	Tuesday, January 30, 2018	Approved
Vim Tux (Portable) 8.0.1431	376	Saturday, January 27, 2018	Approved
Vim Tux (Portable) 8.0.1428	443	Thursday, January 4, 2018	Approved
Vim Tux (Portable) 8.0.1422	383	Saturday, December 30, 2017	Approved
Vim Tux (Portable) 8.0.1390	383	Sunday, December 17, 2017	Approved
Vim Tux (Portable) 8.0.1379	367	Thursday, December 14, 2017	Approved
Vim Tux (Portable) 8.0.1376	412	Thursday, December 7, 2017	Approved
Vim Tux (Portable) 8.0.1358	429	Friday, December 1, 2017	Approved
Vim Tux (Portable) 8.0.1330	394	Thursday, November 23, 2017	Approved
Vim Tux (Portable) 8.0.1311	376	Monday, November 20, 2017	Approved
Vim Tux (Portable) 8.0.1305	375	Saturday, November 18, 2017	Approved
Vim Tux (Portable) 8.0.1272	443	Thursday, November 9, 2017	Approved
Vim Tux (Portable) 8.0.1257	356	Sunday, November 5, 2017	Approved
Vim Tux (Portable) 8.0.1203	438	Wednesday, October 18, 2017	Approved
Vim Tux (Portable) 8.0.1157	457	Friday, September 29, 2017	Approved
Vim Tux (Portable) 8.0.1088	411	Monday, September 11, 2017	Approved
Vim Tux (Portable) 8.0.1010	431	Tuesday, August 29, 2017	Approved
Vim Tux (Portable) 8.0.0987	392	Wednesday, August 23, 2017	Approved
Vim Tux (Portable) 8.0.0737	466	Thursday, July 20, 2017	Approved
Vim Tux (Portable) 8.0.0642	438	Sunday, June 18, 2017	Approved
Vim Tux (Portable) 8.0.0584	441	Wednesday, April 26, 2017	Approved
Vim Tux (Portable) 8.0.0566	361	Friday, April 21, 2017	Approved
Vim Tux (Portable) 8.0.0123	661	Friday, December 9, 2016	Approved
Vim Tux (Portable) 8.0.0117	468	Friday, December 2, 2016	Approved
Vim Tux (Portable) 8.0.0066	452	Thursday, November 10, 2016	Approved
Vim Tux (Portable) 8.0.0051	470	Friday, October 28, 2016	Approved
Vim Tux (Portable) 8.0.0045	486	Friday, October 21, 2016	Approved
Vim Tux (Portable) 8.0.0017	387	Wednesday, September 28, 2016	Approved
Vim Tux (Portable) 8.0.005	495	Friday, September 16, 2016	Approved
Vim Tux (Portable) 7.4.2222	500	Thursday, August 18, 2016	Approved
Vim Tux (Portable) 7.4.2180	462	Tuesday, August 9, 2016	Approved
Vim Tux (Portable) 7.4.2153	427	Friday, August 5, 2016	Approved
Vim Tux (Portable) 7.4.2089	451	Friday, July 22, 2016	Approved
Vim Tux (Portable) 7.4.2034	438	Friday, July 15, 2016	Approved
Vim Tux (Portable) 7.4.1987	461	Sunday, July 3, 2016	Approved
Vim Tux (Portable) 7.4.1949	455	Thursday, June 23, 2016	Approved
Vim Tux (Portable) 7.4.1913	462	Friday, June 10, 2016	Approved
Vim Tux (Portable) 7.4.1905	396	Thursday, June 9, 2016	Approved
Vim Tux (Portable) 7.4.1901	446	Tuesday, June 7, 2016	Approved
Vim Tux (Portable) 7.4.1862	366	Thursday, June 2, 2016	Approved
Vim Tux (Portable) 7.4.1856	430	Monday, May 30, 2016	Approved
Vim Tux (Portable) 7.4.1848	435	Friday, May 27, 2016	Approved
Vim Tux (Portable) 7.4.1842	416	Thursday, May 26, 2016	Approved
Vim Tux (Portable) 7.4.1832	393	Thursday, May 19, 2016	Approved
Vim Tux (Portable) 7.4.1829	497	Thursday, May 12, 2016	Approved
Vim Tux (Portable) 7.4.1824	457	Monday, May 9, 2016	Approved

2023 Vim Team

Release Notes

https://www.vim.org/vim91.php

Dependencies

- vcredist2015 (≥ 14.0.24215.20170201)

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

111,135

5

05 Feb 2025

05 Feb 2025

Vim Tux (Portable)

Vim Tux (Portable) 9.1.1076

(Waiting for Maintainer to take corrective action)

Some Checks Have Failed or Are Not Yet Complete

Pauby (maintainer) on 05 Feb 2025 06:13:38 +00:00:

chocolatey-ops (reviewer) on 05 Feb 2025 06:45:18 +00:00:

Guidelines

Notes

chocolatey-ops (reviewer) on 05 Feb 2025 07:43:13 +00:00:

Notes

Antivirus Detections

Ground Rules: