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.0.nupkg"

### d. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService"

#### ii. If using a Client Salt, add it here
# $ChocolateyCentralManagementClientSalt = "clientsalt"

#### iii. If using a Service Salt, add it here
# $ChocolateyCentralManagementServiceSalt = "servicesalt"

## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository

#### Download the Nupkg, appending .zip to the filename to handle archive cmdlet limitations
if (-not (Get-Command choco.exe -ErrorAction SilentlyContinue)) {
    $TempDirectory = Join-Path $env:Temp "chocolateyInstall"
    if (-not (Test-Path $TempDirectory -PathType Container)) {
        $null = New-Item -Path $TempDirectory -ItemType Directory
    }
    $DownloadedNupkg = Join-Path $TempDirectory "$(Split-Path $ChocolateyDownloadUrl -Leaf).zip"
    Invoke-WebRequest -Uri $ChocolateyDownloadUrl -OutFile $DownloadedNupkg @RequestArguments

    #### Extract the Nupkg, and run the chocolateyInstall script
    if (Get-Command Microsoft.PowerShell.Archive\Expand-Archive -ErrorAction SilentlyContinue) {
        Microsoft.PowerShell.Archive\Expand-Archive -Path $DownloadedNupkg -DestinationPath $TempDirectory -Force
    } else {
        # PowerShell versions <4.0 do not have this function available
        try {
            $shellApplication = New-Object -ComObject Shell.Application
            $zipPackage = $shellApplication.NameSpace($DownloadedNupkg)
            $destinationFolder = $shellApplication.NameSpace($TempDirectory)
            $destinationFolder.CopyHere($zipPackage.Items(), 0x10)
        } catch {
            Write-Warning "Unable to unzip package using built-in compression."
            throw $_
        }
    }

    & $(Join-Path $TempDirectory "tools\chocolateyInstall.ps1")
}

if (-not (Get-Command choco.exe -ErrorAction SilentlyContinue)) {
    refreshenv
}

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# choco feature enable -n useFipsCompliantChecksums

### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
choco config set --name cacheLocation --value C:\ProgramData\chocolatey\cache

#### Increase timeout to at least 4 hours
choco config set --name commandExecutionTimeoutSeconds --value 14400

#### Turn off download progress when running choco through integrations
choco feature disable --name showDownloadProgress

### c. Sources ###
#### Remove the default community package repository source
choco source list --limitoutput | ConvertFrom-Csv -Header 'Name', 'Location' -Delimiter '|' | ForEach-Object {
    if ($_.Location -eq 'https://community.chocolatey.org/api/v2/') {
        choco source remove -n $_.Name
    }
}

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here

#### NOTE: This EXAMPLE may require changes
if ($NugetRepositoryCredential) {
    choco source add --name ChocolateyInternal --source $NugetRepositoryUrl --user $NugetRepositoryCredential.UserName --password $NugetRepositoryCredential.GetNetworkCredential().Password --priority 1
} else {
    choco source add --name ChocolateyInternal --source $NugetRepositoryUrl --priority 1
}

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
choco upgrade chocolatey --confirm

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
choco install chocolatey-license --source $NugetRepositoryUrl --confirm

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
if ("chocolatey-license" -in (choco list --localonly --limitoutput | ConvertFrom-Csv -Header "Name" -Delimiter "|").Name) {
    choco source disable --name chocolatey.licensed
} else {
    Write-Warning "Not disabling 'chocolatey.licensed' feed, as Chocolatey-License has not been installed."
}

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
if ("chocolatey-license" -in (choco list --localonly --limitoutput | ConvertFrom-Csv -Header "Name" -Delimiter "|").Name) {
    choco install chocolatey.extension --source $NugetRepositoryUrl --confirm
} else {
    Write-Warning "Not installing 'chocolatey.extension', as Chocolatey-License has not been installed."
}

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
choco feature disable --name showNonElevatedWarnings
choco feature enable --name useBackgroundService
choco feature enable --name useBackgroundServiceWithNonAdministratorsOnly
choco feature enable --name allowBackgroundServiceUninstallsFromUserInstallsOnly
choco config set --name allowedBackgroundServiceCommands --value "install,upgrade,uninstall"

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if ($ChocolateyCentralManagementUrl) {
    choco install chocolatey-agent --source $NugetRepositoryUrl --confirm
    choco config set --name CentralManagementServiceUrl --value $ChocolateyCentralManagementUrl
    if ($ChocolateyCentralManagementClientSalt) {
        choco config set --name centralManagementClientCommunicationSaltAdditivePassword --value $ChocolateyCentralManagementClientSalt
    }
    if ($ChocolateyCentralManagementServiceSalt) {
        choco config set --name centralManagementServiceCommunicationSaltAdditivePassword --value $ChocolateyCentralManagementServiceSalt
    }
    choco feature enable --name useChocolateyCentralManagement
    choco feature enable --name useChocolateyCentralManagementDeployments
}

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### i. chocolatey.chocolatey
##### You will require the chocolatey.chocolatey collection to be installed
##### on all machines using this playbook.
##### Please see https://github.com/chocolatey/chocolatey-ansible/#installing-the-collection-from-ansible-galaxy

- name: Install and Configure Chocolatey
  hosts: all

## 2. TOP LEVEL VARIABLES ##
  vars:

### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
    nuget_repository_url: INTERNAL REPO URL

### b. Internal Repository Credential ###
#### If required, add the repository access credential here and
#### uncomment lines with source_username and source_password below
#    nuget_repository_username: username
#    nuget_repository_password: password

### c. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
#    chocolatey_central_management_url: https://chocolatey-central-management:24020/ChocolateyManagementService

#### ii. If using a Client Salt, add it here
#    chocolatey_central_management_client_salt: clientsalt

#### iii. If using a Service Salt, add it here
#    chocolatey_central_management_service_salt: servicesalt

## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository

  tasks:
  - name: Install chocolatey
    win_chocolatey:
      name: chocolatey
      source: ""{{ nuget_repository_url }}""
      # source_username: ""{{ nuget_repository_username }}""
      # source_password: ""{{ nuget_repository_password }}""

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
#   - name: Enable FIPS compliance
#     win_chocolatey_feature:
#       name: useFipsCompliantChecksums
#       state: enabled

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
  - name: Set the cache location
    win_chocolatey_config:
      name: cacheLocation
      state: present
      value: C:\ProgramData\chocolatey\cache

#### Increase timeout to at least 4 hours
  - name: Set the command execution timeout
    win_chocolatey_config:
      name: commandExecutionTimeoutSeconds
      state: present
      value: 14400

#### Turn off download progress when running choco through integrations
  - name: Disable showing download progress
    win_chocolatey_feature:
      name: showDownloadProgress
      state: disabled

### c. Sources ###
#### Remove the default community package repository source
  - name: Remove Chocolatey Community Repository
    win_chocolatey_source:
      name: chocolatey
      state: absent

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE may require changes
  - name: Add Internal Repository
    win_chocolatey_source:
      name: ChocolateyInternal
      state: present
      source: {{ nuget_repository_url }}
      # source_username: {{ nuget_repository_username }}
      # source_password: {{ nuget_repository_password }}
      priority: 1

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
  - name: Upgrade Chocolatey
    win_chocolatey:
      name: chocolatey
      state: latest

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
  - name: Install Chocolatey License
    win_chocolatey:
      name: chocolatey-license
      source: ChocolateyInternal
      state: latest

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
  - name: Disable Chocolatey Community Repository
    win_chocolatey_source:
      name: chocolatey.licensed
      state: disabled

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
  - name: Install Chocolatey Extension
    win_chocolatey:
      name: chocolatey.extension
      source: ChocolateyInternal
      state: latest

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
  - name: Hide not-elevated warnings
    win_chocolatey_feature:
      name: showNonElevatedWarnings
      state: disabled

  - name: Use background mode for self-service
    win_chocolatey_feature:
      name: useBackgroundService
      state: enabled

  - name: Use background service for non-admins
    win_chocolatey_feature:
      name: useBackgroundServiceWithNonAdministratorsOnly
      state: enabled

  - name: Allow background uninstallation for user installs
    win_chocolatey_feature:
      name: allowBackgroundServiceUninstallsFromUserInstallsOnly
      state: enabled

  - name: Set allowed background service commands
    win_chocolatey_config:
      name: backgroundServiceAllowedCommands
      state: present
      value: install,upgrade,uninstall

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
  - name: Install Chocolatey Agent
    when: chocolatey_central_management_url is defined
    win_chocolatey:
      name: chocolatey-agent
      source: ChocolateyInternal
      state: latest

  - name: Set the Central Management Service URL
    when: chocolatey_central_management_url is defined
    win_chocolatey_config:
      name: CentralManagementServiceUrl
      state: present
      value: {{ chocolatey_central_management_url }}

  - name: Set the Central Management Client Salt
    when: chocolatey_central_management_client_salt is defined
    win_chocolatey_config:
      name: centralManagementClientCommunicationSaltAdditivePassword
      state: present
      value: {{ chocolatey_central_management_client_salt }}

  - name: Set the Central Management Service Salt
    when: chocolatey_central_management_service_salt is defined
    win_chocolatey_config:
      name: centralManagementServiceCommunicationSaltAdditivePassword
      state: present
      value: {{ chocolatey_central_management_service_salt }}

  - name: Use Central Management
    when: chocolatey_central_management_url is defined
    win_chocolatey_feature:
      name: useChocolateyCentralManagement
      state: enabled

  - name: Use Central Management Deployments
    when: chocolatey_central_management_url is defined
    win_chocolatey_feature:
      name: useChocolateyCentralManagementDeployments
      state: enabled

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

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### The Chocolatey resources are available with any recent version of Chef.
#### We utilise the Chocolatey recipe to install the Chocolatey binaries.
include_recipe "chocolatey"

## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
NugetRepositoryUrl = "INTERNAL REPO URL"

### b. Internal Repository Credential ###
#### If required, add the repository access credential here
# NugetRepositoryUsername = "username"
# NugetRepositoryPassword = "password"

### c. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
ChocolateyNupkgUrl = "INTERNAL REPO URL/package/chocolatey.2.4.0.nupkg",

### d. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService"

#### ii. If using a Client Salt, add it here
# ChocolateyCentralManagementClientSalt = "clientsalt"

#### iii. If using a Service Salt, add it here
# ChocolateyCentralManagementServiceSalt = "servicesalt"

## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
node['chocolatey']['install vars'] = {
  'chocolateyDownloadUrl' => "#{ChocolateyNupkgUrl}",
}

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# chocolatey_feature 'useFipsCompliantChecksums' do
#   action :enable
# end

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
chocolatey_config 'cacheLocation' do
  value 'C:\ProgramData\chocolatey\cache'
end

#### Increase timeout to at least 4 hours
chocolatey_config 'commandExecutionTimeoutSeconds' do
  value '14400'
end

#### Turn off download progress when running choco through integrations
chocolatey_feature 'showDownloadProgress' do
  action :disable
end

### c. Sources ###
#### Remove the default community package repository source
chocolatey_source 'chocolatey' do
  action :remove
end

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here

#### NOTE: This EXAMPLE may require changes
chocolatey_source 'ChocolateyInternal' do
  source "#{NugetRepositoryUrl}"
  priority 1
  action   :add
end

execute 'ChocolateyInternal' do
  command "choco source add --name ChocolateyInternal -s #{NugetRepositoryUrl} -u=#{NugetRepositoryUsername} -p=#{NugetRepositoryPassword} --priority=1"
  only_if { NugetRepositoryUsername != nil || NugetRepositoryPassword != nil }
end

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
chocolatey_package 'chocolatey' do
  action :upgrade
  source "#{NugetRepositoryUrl}"
end

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
chocolatey_package 'chocolatey-license' do
  action :install
  source "#{NugetRepositoryUrl}"
end

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
chocolatey_source 'chocolatey.licensed' do
  action            :disable
end

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
chocolatey_package 'chocolatey.extention' do
  action     install
  source     "#{NugetRepositoryUrl}"
end

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
chocolatey_feature 'showNonElevatedWarnings' do
  action :disable
end

chocolatey_feature 'useBackgroundService' do
  action :enable
end

chocolatey_feature 'useBackgroundServiceWithNonAdministratorsOnly' do
  action :enable
end

chocolatey_feature 'allowBackgroundServiceUninstallsFromUserInstallsOnly' do
  action :enable
end

chocolatey_config 'backgroundServiceAllowedCommands' do
  value 'install,upgrade,uninstall'
end

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
chocolatey_package 'chocolatey-agent' do
  action     install
  source     "#{NugetRepositoryUrl}"
  # user       "#{NugetRepositoryUsername}"
  # password   "#{NugetRepositoryPassword}"
  only_if { ChocolateyCentralManagementUrl != nil }
end

chocolatey_config 'CentralManagementServiceUrl' do
  value  "#{ChocolateyCentralManagementUrl}"
  only_if { ChocolateyCentralManagementUrl != nil }
end

chocolatey_config 'centralManagementClientCommunicationSaltAdditivePassword' do
  value   "#{ChocolateyCentralManagementClientSalt}"
  only_if { ChocolateyCentralManagementClientSalt != nil }
end

chocolatey_config 'centralManagementServiceCommunicationSaltAdditivePassword' do
  value   "#{ChocolateyCentralManagementServiceSalt}"
  only_if { ChocolateyCentralManagementServiceSalt != nil }
end

chocolatey_feature 'useChocolateyCentralManagement' do
  action :enable
  only_if { ChocolateyCentralManagementUrl != nil }
end

chocolatey_feature 'useChocolateyCentralManagementDeployments' do
  action :enable
  only_if { ChocolateyCentralManagementUrl != nil }
end

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

If Applicable - Chocolatey Configuration/Installation


#requires -Modules cChoco
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### i. Requires chocolatey\cChoco DSC module to be installed on the machine compiling the DSC manifest
#### NOTE: This will need to be installed before running the DSC portion of this script
if (-not (Get-Module cChoco -ListAvailable)) {
    $null = Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
    if (($PSGallery = Get-PSRepository -Name PSGallery).InstallationPolicy -ne "Trusted") {
        Set-PSRepository -Name PSGallery -InstallationPolicy Trusted
    }
    Install-Module -Name cChoco
    if ($PSGallery.InstallationPolicy -ne "Trusted") {
        Set-PSRepository -Name PSGallery -InstallationPolicy $PSGallery.InstallationPolicy
    }
}

#### ii. Requires a hosted copy of the install.ps1 script
##### This should be available to download without authentication.
##### The original script can be found here: https://community.chocolatey.org/install.ps1

Configuration ChocolateyConfig {
## 2. TOP LEVEL VARIABLES ##
    param(
### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
        $NugetRepositoryUrl      = "INTERNAL REPO URL",

### b. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
        $ChocolateyNupkgUrl      = "INTERNAL REPO URL/package/chocolatey.2.4.0.nupkg",

### c. Internal Repository Credential ###
#### If required, add the repository access credential here
#        $NugetRepositoryCredential = [PSCredential]::new(
#            "username",
#            ("password" | ConvertTo-SecureString -AsPlainText -Force)
#        ),

### d. Install.ps1 URL
#### The path to the hosted install script:
        $ChocolateyInstallPs1Url = "https://community.chocolatey.org/install.ps1"

### e. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
#        $ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService",

#### ii. If using a Client Salt, add it here
#        $ChocolateyCentralManagementClientSalt = "clientsalt",

#### iii. If using a Service Salt, add it here
#        $ChocolateyCentralManagementServiceSalt = "servicesalt"
    )
    Import-DscResource -ModuleName PSDesiredStateConfiguration
    Import-DscResource -ModuleName cChoco

    Node 'localhost' {
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
        Environment chocoDownloadUrl {
            Name  = "chocolateyDownloadUrl"
            Value = $ChocolateyNupkgUrl
        }

        cChocoInstaller installChocolatey {
            DependsOn = "[Environment]chocoDownloadUrl"
            InstallDir = Join-Path $env:ProgramData "chocolatey"
            ChocoInstallScriptUrl = $ChocolateyInstallPs1Url
        }

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
#        cChocoFeature featureFipsCompliance {
#            FeatureName = "useFipsCompliantChecksums"
#        }

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
        cChocoConfig cacheLocation {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            ConfigName = "cacheLocation"
            Value      = "C:\ProgramData\chocolatey\cache"
        }

#### Increase timeout to at least 4 hours
        cChocoConfig commandExecutionTimeoutSeconds {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            ConfigName = "commandExecutionTimeoutSeconds"
            Value      = 14400
        }

#### Turn off download progress when running choco through integrations
        cChocoFeature showDownloadProgress {
            DependsOn   = "[cChocoInstaller]installChocolatey"
            FeatureName = "showDownloadProgress"
            Ensure      = "Absent"
        }

### c. Sources ###
#### Remove the default community package repository source
        cChocoSource removeCommunityRepository {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            Name       = "chocolatey"
            Ensure     = "Absent"
        }

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here.
#### NOTE: This EXAMPLE may require changes
        cChocoSource addInternalSource {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            Name        = "ChocolateyInternal"
            Source      = $NugetRepositoryUrl
            Credentials = $NugetRepositoryCredential
            Priority    = 1
        }

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
        cChocoPackageInstaller updateChocolatey {
            DependsOn   = "[cChocoSource]addInternalSource", "[cChocoSource]removeCommunityRepository"
            Name        = "chocolatey"
            AutoUpgrade = $true
        }

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
        cChocoPackageInstaller chocolateyLicense {
            DependsOn = "[cChocoPackageInstaller]updateChocolatey"
            Name      = "chocolatey-license"
        }

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
        Script disableLicensedSource {
            DependsOn  = "[cChocoPackageInstaller]chocolateyLicense"
            GetScript  = {
                $Source = choco source list --limitoutput | `
                    ConvertFrom-Csv -Delimiter '|' -Header Name, Source, Disabled | `
                    Where-Object Name -eq "chocolatey.licensed"

                return @{
                    Result = if ($Source) {
                        [bool]::Parse($Source.Disabled)
                    } else {
                        Write-Warning "Source 'chocolatey.licensed' was not present."
                        $true  # Source does not need disabling
                    }
                }
            }
            SetScript  = {
                $null = choco source disable --name "chocolatey.licensed"
            }
            TestScript = {
                $State = [ScriptBlock]::Create($GetScript).Invoke()
                return $State.Result
            }
        }

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
        cChocoPackageInstaller chocolateyLicensedExtension {
            DependsOn = "[Script]disableLicensedSource"
            Name      = "chocolatey.extension"
        }

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
        cChocoFeature hideElevatedWarnings {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "showNonElevatedWarnings"
            Ensure      = "Absent"
        }

        cChocoFeature useBackgroundService {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "useBackgroundService"
            Ensure      = "Present"
        }

        cChocoFeature useBackgroundServiceWithNonAdmins {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "useBackgroundServiceWithNonAdministratorsOnly"
            Ensure      = "Present"
        }

        cChocoFeature useBackgroundServiceUninstallsForUserInstalls {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "allowBackgroundServiceUninstallsFromUserInstallsOnly"
            Ensure      = "Present"
        }

        cChocoConfig allowedBackgroundServiceCommands {
            DependsOn   = "[cChocoFeature]useBackgroundService"
            ConfigName = "backgroundServiceAllowedCommands"
            Value       = "install,upgrade,uninstall"
        }

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
        if ($ChocolateyCentralManagementUrl) {
            cChocoPackageInstaller chocolateyAgent {
                DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
                Name      = "chocolatey-agent"
            }

            cChocoConfig centralManagementServiceUrl {
                DependsOn   = "[cChocoPackageInstaller]chocolateyAgent"
                ConfigName = "CentralManagementServiceUrl"
                Value       = $ChocolateyCentralManagementUrl
            }

            if ($ChocolateyCentralManagementClientSalt) {
                cChocoConfig centralManagementClientSalt {
                    DependsOn  = "[cChocoPackageInstaller]chocolateyAgent"
                    ConfigName = "centralManagementClientCommunicationSaltAdditivePassword"
                    Value      = $ChocolateyCentralManagementClientSalt
                }
            }

            if ($ChocolateyCentralManagementServiceSalt) {
                cChocoConfig centralManagementServiceSalt {
                    DependsOn  = "[cChocoPackageInstaller]chocolateyAgent"
                    ConfigName = "centralManagementServiceCommunicationSaltAdditivePassword"
                    Value      = $ChocolateyCentralManagementServiceSalt
                }
            }

            cChocoFeature useCentralManagement {
                DependsOn   = "[cChocoPackageInstaller]chocolateyAgent"
                FeatureName = "useChocolateyCentralManagement"
                Ensure      = "Present"
            }

            cChocoFeature useCentralManagementDeployments {
                DependsOn   = "[cChocoPackageInstaller]chocolateyAgent"
                FeatureName = "useChocolateyCentralManagementDeployments"
                Ensure      = "Present"
            }
        }
    }
}

# If working this into an existing configuration with a good method for
$ConfigData = @{
    AllNodes = @(
        @{
            NodeName                    = "localhost"
            PSDscAllowPlainTextPassword = $true
        }
    )
}

try {
    Push-Location $env:Temp
    $Config = ChocolateyConfig -ConfigurationData $ConfigData
    Start-DscConfiguration -Path $Config.PSParentPath -Wait -Verbose -Force
} finally {
    Pop-Location
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### i. Requires puppetlabs/chocolatey module
####  See https://forge.puppet.com/puppetlabs/chocolatey


## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$_repository_url = 'INTERNAL REPO URL'

### b. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
$_choco_download_url = 'INTERNAL REPO URL/package/chocolatey.2.4.0.nupkg'

### c. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $_chocolatey_central_management_url = 'https://chocolatey-central-management:24020/ChocolateyManagementService'

#### ii. If using a Client Salt, add it here
# $_chocolatey_central_management_client_salt = "clientsalt"

#### iii. If using a Service Salt, add it here
# $_chocolatey_central_management_service_salt = 'servicesalt'


## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
### Note: `chocolatey_download_url is completely different than normal
###  source locations. This is directly to the bare download url for the
###  chocolatey.nupkg, similar to what you see when you browse to
###  https://community.chocolatey.org/api/v2/package/chocolatey
class {'chocolatey':
  chocolatey_download_url => $_choco_download_url,
  use_7zip                => false,
}


## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations

#chocolateyfeature {'useFipsCompliantChecksums':
#  ensure => enabled,
#}

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
chocolateyconfig {'cacheLocation':
  value => 'C:\ProgramData\chocolatey\cache',
}

#### Increase timeout to at least 4 hours
chocolateyconfig {'commandExecutionTimeoutSeconds':
  value => '14400',
}

#### Turn off download progress when running choco through integrations
chocolateyfeature {'showDownloadProgress':
  ensure => disabled,
}

### c. Sources ###
#### Remove the default community package repository source
chocolateysource {'chocolatey':
  ensure   => absent,
  location => 'https://community.chocolatey.org/api/v2/',
}

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here

#### NOTE: This EXAMPLE requires changes
chocolateysource {'internal_chocolatey':
  ensure             => present,
  location           => $_repository_url,
  priority           => 1,
  username           => 'optional',
  password           => 'optional,not ensured',
  bypass_proxy       => true,
  admin_only         => false,
  allow_self_service => false,
}

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/

package {'chocolatey':
  ensure   => latest,
  provider => chocolatey,
  source   => $_repository_url,
}


## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/guides/organizations/organizational-deployment-guide#exercise-4-create-a-package-for-the-license

# TODO: Add resource for installing/ensuring the chocolatey-license package
package {'chocolatey-license':
  ensure   => latest,
  provider => chocolatey,
  source   => $_repository_url,
}

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
## Disabled sources still need all other attributes until
## https://tickets.puppetlabs.com/browse/MODULES-4449 is resolved.
## Password is necessary with user, but not ensurable, so it should not
## matter what it is set to here. If you ever do get into trouble here,
## the password is your license GUID.
chocolateysource {'chocolatey.licensed':
  ensure   => disabled,
  priority => '10',
  user     => 'customer',
  password => '1234',
  require  => Package['chocolatey-license'],
}

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
package {'chocolatey.extension':
  ensure   => latest,
  provider => chocolatey,
  source   => $_repository_url,
  require  => Package['chocolatey-license'],
}

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
chocolateyfeature {'showNonElevatedWarnings':
  ensure => disabled,
}

chocolateyfeature {'useBackgroundService':
  ensure => enabled,
}

chocolateyfeature {'useBackgroundServiceWithNonAdministratorsOnly':
  ensure => enabled,
}

chocolateyfeature {'allowBackgroundServiceUninstallsFromUserInstallsOnly':
  ensure => enabled,
}

chocolateyconfig {'backgroundServiceAllowedCommands':
  value => 'install,upgrade,uninstall',
}

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if $_chocolatey_central_management_url {
  package {'chocolatey-agent':
    ensure   => latest,
    provider => chocolatey,
    source   => $_repository_url,
    require  => Package['chocolatey-license'],
  }

  chocolateyconfig {'CentralManagementServiceUrl':
    value   => $_chocolatey_central_management_url,
  }

  if $_chocolatey_central_management_client_salt {
    chocolateyconfig {'centralManagementClientCommunicationSaltAdditivePassword':
      value => $_chocolatey_central_management_client_salt,
    }
  }

  if $_chocolatey_central_management_service_salt {
    chocolateyconfig {'centralManagementClientCommunicationSaltAdditivePassword':
      value => $_chocolatey_central_management_client_salt,
    }
  }

  chocolateyfeature {'useChocolateyCentralManagement':
    ensure  => enabled,
    require => Package['chocolatey-agent'],
  }

  chocolateyfeature {'useChocolateyCentralManagementDeployments':
    ensure  => enabled,
    require => Package['chocolatey-agent'],
  }
}

Need Help? View our docs or file an issue.

There is already a version of this package in your Script Builder

Current Version	New Version

Downloads:

153,356

Downloads of v 9.1.837:

12

Last Update:

04 Nov 2024

Package Maintainer(s):

Pauby

Software Author(s):

TuxProject.de
Vim Team

Tags:

vim-tux vim editor tux admin

Vim Tux (Install)

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

9.1.837 | Updated: 04 Nov 2024

Downloads:

153,356

Downloads of v 9.1.837:

Maintainer(s):

Pauby

Software Author(s):

TuxProject.de
Vim Team

Tags:

vim-tux vim editor tux admin

Vim Tux (Install) 9.1.837

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

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 Passed

Details

Scan Testing Resulted in Flagged as a Note:

At least one file within this package has greater than 0 detections, but less than 5

Details

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Vim Tux (Install), run the following command from the command line or from PowerShell:

To upgrade Vim Tux (Install), run the following command from the command line or from PowerShell:

To uninstall Vim Tux (Install), run the following command from the command line or from PowerShell:

NOTE

This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)

Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download

Option 2: Internalized Package (Reliable, Scalable)

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

Package Internalizer (C4B)

Run: (additional options)

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

For package and dependencies run:

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

Automate package internalization

3. Copy Your Script

choco upgrade vim-tux.install -y --source="'INTERNAL REPO URL'" --version="'9.1.837'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade vim-tux.install -y --source="'INTERNAL REPO URL'" --version="'9.1.837'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode


- name: Install vim-tux.install
  win_chocolatey:
    name: vim-tux.install
    version: '9.1.837'
    source: INTERNAL REPO URL
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'vim-tux.install' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '9.1.837'
end

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


cChocoPackageInstaller vim-tux.install
{
    Name     = "vim-tux.install"
    Version  = "9.1.837"
    Source   = "INTERNAL REPO URL"
}

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


package { 'vim-tux.install':
  ensure   => '9.1.837',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

NOTE

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

WARNING

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

Package Approved

This package was approved as a trusted package on 04 Nov 2024.

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.

Package Parameters

The following package parameters can be set:

/InstallDir - Install to a specific location.
/InstallPopUp - Install into the context menu "Edit with gVim", powered by GVimExt.dll.
/RestartExplorer - Kill explorer.exe before each update to free up the in-use GVimExt.dll.
/NoCreateBatFiles - Do not create batch files in C:\Windows (vim.bat, vimdiff.bat, etc).

For example choco install vim-tux.portable --package-parameters="'/InstallDir=C:\MyFolder /InstallPopUp /RestartExplorer'"

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

Notes

The Vim mailing list Url causes Package Validation to regularly fail, so it was removed from the metadata.
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\.skipAutoUninstall

tools\chocolateyInstall.ps1

$ErrorActionPreference = 'Stop'

$toolsDir = Split-Path -Parent $MyInvocation.MyCommand.Definition
$versPath = 'vim91'
#$filename32 = "$toolsDir\complete-x86.7z"
$filename64 = "$toolsDir\complete-x64.7z"

# package parameter defaults
$destDir = Join-Path -Path $env:ProgramFiles -ChildPath "Vim\$versPath"
$createBatFiles = '-create-batfiles vim gvim evim view gview vimdiff gvimdiff'
$installPopUp = $null

$pp = Get-PackageParameters

if ($pp['InstallDir']) {
    $destDir = $pp['InstallDir']
    $destDir = $destDir -replace '^[''"]|[''"]$' # Strip quotations. Necessary?
    $destDir = $destDir -replace '[\/]$' # Remove any slashes from end of line
    if (-not ($destDir.EndsWith($versPath))) {
        # installer will not run outside folder vim90
        $destDir = Join-Path -Path $destDir -ChildPath $versPath
    }
}

# Optionally restart explorer before install
if ($pp['RestartExplorer']) {
    Write-Debug "Restarting Explorer."
    Get-Process -Name 'explorer' | Stop-Process -Force
}

# Create batch files in C:\Windows by default
if ($pp['NoCreateBatFiles']) {
    Write-Debug 'Not installing batch files.'
    $createBatFiles = $null
}

# Do not install context menu entry by default
if ($pp['InstallPopUp']) {
    Write-Debug 'Installing context menu entry.'
    $installPopUp = '-install-popup'
}

$baseArgs = "-install-openwith -add-start-menu"
$installArgs = $installPopUp, $createBatFiles, $baseArgs -ne $null -join ' '

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

Get-ChocolateyUnzip @packageArgs

# Supplied manifest fixes useless UAC request
Move-Item -Path "$toolsDir\patch.exe.manifest" -Destination $destDir -Force -ErrorAction SilentlyContinue
(Get-Item $destdir\patch.exe).LastWriteTime = (Get-Date) # exe must be newer than manifest

# Run vim's installer
Move-Item -Path "$toolsDir\install.exe" -Destination "$destDir\install.exe" -Force -ErrorAction SilentlyContinue # vim-tux removed the installer, just in time for Defender to stop flagging it
Move-Item -Path "$toolsDir\uninstall.exe" -Destination "$destDir\uninstall.exe" -Force -ErrorAction SilentlyContinue # vim-tux removed the uninstaller, just in time for Defender to stop flagging it
Start-ChocolateyProcessAsAdmin -Statements "$installArgs" -ExeToRun "$destDir\install.exe" -ValidExitCodes '0' | Out-Null
#$filename32, 
$filename64 | Remove-Item -Force -ErrorAction SilentlyContinue
Write-Host 'Build provided by TuxProject.de - consider donating to help support their server costs.'

tools\chocolateyUninstall.ps1

$ErrorActionPreference = 'Stop'

$versPath = 'vim91'
$destDir = Join-Path -Path $env:ProgramFiles -ChildPath "Vim"

# Apparently doesn't have a non-interactive mode. Send 'y' to its input
Set-Content -Path "$env:TEMP\vimuninstallinput" -Value 'y'
Start-Process -FilePath "$destDir\$versPath\uninstall.exe" -ArgumentList '-nsis' -RedirectStandardInput "$env:TEMP\vimuninstallinput" -Wait
Remove-Item "$env:TEMP\vimuninstallinput"
Remove-Item $destDir -Force -Recurse

tools\complete-x64.7z

md5: E64069CBFA329E6C71986F86037F6B0C | sha1: 6EF12D0BC70B5B7CADAC9707A2BCC325D7B9491F | sha256: 478BFB84BFF53BC4275A8F5733BC5A2B4262B89A844779DBDA3343F7E122D81D | sha512: F4B818C2389315B4A625128F4027A9122076BB6301B79577F9B7195DE63CDEFCB60483803FA6C1A353B2D43A994D5E288D10D6F631B66370ED9E9BB59C707F21

tools\install.exe

md5: 364AFC57AFA77D71D72F6ECE0B8975C5 | sha1: 689D93FECEE9E1CAAF83020C6A5A2150215F30E8 | sha256: 0C651F1118A50244FFE328193ECEF6F8846429A1F466DE3F65D512CD3D189A9E | sha512: 61E619A1BEBF64F0B815BEFDD826C8AAE4817A6256953A9B235E3F097BAAA0649980CD42314616988716620EC55F911BC0FD19DC2FF93367E0C643C864217793

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\patch.exe.manifest

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
    <security>
      <requestedPrivileges>
        <!-- Make sure that UAC believes
        that it does not require administrative privilege -->
        <requestedExecutionLevel level="asInvoker" uiAccess="false"/>
      </requestedPrivileges>
    </security>
  </trustInfo>
</assembly>

tools\uninstall.exe

md5: 5689F6B9585739A1E555ECDC76E1044A | sha1: 6A7AFE93C90ED5AA8767DD3B674871095014178F | sha256: 8ED17A85A58FDE4B2200774EF591385D28F336BA0F8813FE74AA71599A4D97F7 | sha512: B92E1AF98E6F13823011D0216AFA44090F234DF5FA41CD4DBF065EBDFFB68C4A8F465C44D4D4E4304E4207253518E0696532D675FB1782DA4046FD07DAD0506F

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: 478BFB84BFF53BC4275A8F5733BC5A2B4262B89A844779DBDA3343F7E122D81D (SHA256)


    The install.exe and the uninstall.exe were extracted from https://github.com/vim/vim-win32-installer/releases/download/v9.1.0837/gvim_9.1.0837_x86.zip

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

Virus Scan Results

complete-x64.7z (478bfb84bff5) - ## / 60
vim-tux.install.9.1.837.nupkg (a0f46e0a5bad) - ## / 48
install.exe (0c651f1118a5) - ## / 72
uninstall.exe (8ed17a85a58f) - ## / 72

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version History

Version	Downloads	Last Updated	Status
Vim Tux (Install) 9.1.880	18	Wednesday, November 20, 2024	Approved
Vim Tux (Install) 9.1.869	28	Tuesday, November 19, 2024	Approved
Vim Tux (Install) 9.1.866	34	Friday, November 15, 2024	Approved
Vim Tux (Install) 9.1.861	24	Wednesday, November 13, 2024	Approved
Vim Tux (Install) 9.1.849	35	Monday, November 11, 2024	Approved
Vim Tux (Install) 9.1.847	8	Friday, November 8, 2024	Waiting for Maintainer
Vim Tux (Install) 9.1.842	64	Tuesday, November 5, 2024	Approved
Vim Tux (Install) 9.1.837	12	Monday, November 4, 2024	Approved
Vim Tux (Install) 9.1.818	52	Monday, October 28, 2024	Approved
Vim Tux (Install) 9.1.813	5	Thursday, October 24, 2024	Waiting for Maintainer
Vim Tux (Install) 9.1.810	54	Thursday, October 24, 2024	Approved
Vim Tux (Install) 9.1.792	52	Saturday, October 19, 2024	Approved
Vim Tux (Install) 9.1.785	39	Tuesday, October 15, 2024	Approved
Vim Tux (Install) 9.1.766	13	Wednesday, October 9, 2024	Approved
Vim Tux (Install) 9.1.758	12	Saturday, October 5, 2024	Approved
Vim Tux (Install) 9.1.757	16	Friday, October 4, 2024	Approved
Vim Tux (Install) 9.1.740	110	Tuesday, September 24, 2024	Exempted
Vim Tux (Install) 9.1.733	58	Monday, September 16, 2024	Approved
Vim Tux (Install) 9.1.730	34	Saturday, September 14, 2024	Approved
Vim Tux (Install) 9.1.724	36	Wednesday, September 11, 2024	Approved
Vim Tux (Install) 9.1.722	29	Tuesday, September 10, 2024	Approved
Vim Tux (Install) 9.1.718	32	Friday, September 6, 2024	Approved
Vim Tux (Install) 9.1.714	25	Thursday, September 5, 2024	Approved
Vim Tux (Install) 9.1.708	61	Monday, September 2, 2024	Approved
Vim Tux (Install) 9.1.702	46	Thursday, August 29, 2024	Approved
Vim Tux (Install) 9.1.697	44	Monday, August 26, 2024	Approved
Vim Tux (Install) 9.1.689	32	Friday, August 23, 2024	Approved
Vim Tux (Install) 9.1.682	53	Tuesday, August 20, 2024	Approved
Vim Tux (Install) 9.1.679	39	Sunday, August 18, 2024	Approved
Vim Tux (Install) 9.1.674	48	Thursday, August 15, 2024	Approved
Vim Tux (Install) 9.1.672	36	Monday, August 12, 2024	Approved
Vim Tux (Install) 9.1.668	31	Saturday, August 10, 2024	Approved
Vim Tux (Install) 9.1.661	51	Tuesday, August 6, 2024	Approved
Vim Tux (Install) 9.1.618	84	Saturday, July 27, 2024	Approved
Vim Tux (Install) 9.1.611	43	Wednesday, July 24, 2024	Approved
Vim Tux (Install) 9.1.602	40	Friday, July 19, 2024	Approved
Vim Tux (Install) 9.1.598	31	Friday, July 19, 2024	Approved
Vim Tux (Install) 9.1.589	38	Tuesday, July 16, 2024	Approved
Vim Tux (Install) 9.1.586	25	Tuesday, July 16, 2024	Approved
Vim Tux (Install) 9.1.554	53	Thursday, July 11, 2024	Approved
Vim Tux (Install) 9.1.546	31	Tuesday, July 9, 2024	Approved
Vim Tux (Install) 9.1.544	36	Tuesday, July 9, 2024	Approved
Vim Tux (Install) 9.1.531	40	Saturday, July 6, 2024	Approved
Vim Tux (Install) 9.1.519	36	Thursday, July 4, 2024	Approved
Vim Tux (Install) 9.1.516	67	Monday, June 24, 2024	Approved
Vim Tux (Install) 9.1.514	41	Sunday, June 23, 2024	Approved
Vim Tux (Install) 9.1.512	26	Saturday, June 22, 2024	Approved
Vim Tux (Install) 9.1.505	34	Thursday, June 20, 2024	Approved
Vim Tux (Install) 9.1.500	42	Wednesday, June 19, 2024	Approved
Vim Tux (Install) 9.1.487	54	Saturday, June 15, 2024	Approved
Vim Tux (Install) 9.1.474	54	Tuesday, June 11, 2024	Approved
Vim Tux (Install) 9.1.472	28	Monday, June 10, 2024	Approved
Vim Tux (Install) 9.1.470	68	Thursday, June 6, 2024	Approved
Vim Tux (Install) 9.1.466	35	Thursday, June 6, 2024	Approved
Vim Tux (Install) 9.1.465	44	Wednesday, June 5, 2024	Approved
Vim Tux (Install) 9.1.461	30	Tuesday, June 4, 2024	Approved
Vim Tux (Install) 9.1.454	45	Saturday, June 1, 2024	Approved
Vim Tux (Install) 9.1.448	60	Thursday, May 30, 2024	Approved
Vim Tux (Install) 9.1.447	45	Tuesday, May 28, 2024	Approved
Vim Tux (Install) 9.1.442	61	Saturday, May 25, 2024	Approved
Vim Tux (Install) 9.1.433	34	Friday, May 24, 2024	Approved
Vim Tux (Install) 9.1.432	37	Thursday, May 23, 2024	Approved
Vim Tux (Install) 9.1.426	40	Wednesday, May 22, 2024	Approved
Vim Tux (Install) 9.1.412	41	Tuesday, May 21, 2024	Approved
Vim Tux (Install) 9.1.411	81	Monday, May 13, 2024	Approved
Vim Tux (Install) 9.1.407	54	Sunday, May 12, 2024	Approved
Vim Tux (Install) 9.1.393	63	Wednesday, May 8, 2024	Approved
Vim Tux (Install) 9.1.386	74	Thursday, May 2, 2024	Approved
Vim Tux (Install) 9.1.380	29	Tuesday, April 30, 2024	Approved
Vim Tux (Install) 9.1.373	27	Saturday, April 27, 2024	Approved
Vim Tux (Install) 9.1.368	75	Thursday, April 25, 2024	Approved
Vim Tux (Install) 9.1.366	29	Wednesday, April 24, 2024	Approved
Vim Tux (Install) 9.1.354	58	Saturday, April 20, 2024	Approved
Vim Tux (Install) 9.1.336	55	Tuesday, April 16, 2024	Approved
Vim Tux (Install) 9.1.330	52	Monday, April 15, 2024	Approved
Vim Tux (Install) 9.1.296	63	Thursday, April 11, 2024	Approved
Vim Tux (Install) 9.1.193	118	Friday, March 22, 2024	Approved
Vim Tux (Install) 9.1.186	53	Tuesday, March 19, 2024	Approved
Vim Tux (Install) 9.1.181	52	Friday, March 15, 2024	Approved
Vim Tux (Install) 9.1.113	182	Friday, February 16, 2024	Approved
Vim Tux (Install) 9.1.67	135	Friday, February 2, 2024	Approved
Vim Tux (Install) 9.0.2181	203	Thursday, December 21, 2023	Approved
Vim Tux (Install) 9.0.2167	72	Friday, December 15, 2023	Approved
Vim Tux (Install) 9.0.2155	96	Saturday, December 9, 2023	Approved
Vim Tux (Install) 9.0.2146	82	Tuesday, December 5, 2023	Approved
Vim Tux (Install) 9.0.2134	78	Wednesday, November 29, 2023	Approved
Vim Tux (Install) 9.0.2122	85	Friday, November 24, 2023	Approved
Vim Tux (Install) 9.0.2120	67	Wednesday, November 22, 2023	Approved
Vim Tux (Install) 9.0.2103	108	Tuesday, November 14, 2023	Approved
Vim Tux (Install) 9.0.2095	91	Friday, November 10, 2023	Approved
Vim Tux (Install) 9.0.2092	81	Tuesday, November 7, 2023	Approved
Vim Tux (Install) 9.0.2081	82	Wednesday, November 1, 2023	Approved
Vim Tux (Install) 9.0.2077	76	Saturday, October 28, 2023	Approved
Vim Tux (Install) 9.0.2067	87	Friday, October 27, 2023	Approved
Vim Tux (Install) 9.0.2063	93	Tuesday, October 24, 2023	Approved
Vim Tux (Install) 9.0.2053	108	Friday, October 20, 2023	Approved
Vim Tux (Install) 9.0.2050	53	Thursday, October 19, 2023	Approved
Vim Tux (Install) 9.0.2048	66	Thursday, October 19, 2023	Approved
Vim Tux (Install) 9.0.2043	64	Wednesday, October 18, 2023	Approved
Vim Tux (Install) 9.0.2034	86	Tuesday, October 17, 2023	Approved
Vim Tux (Install) 9.0.2009	99	Tuesday, October 10, 2023	Approved
Vim Tux (Install) 9.0.1976	71	Wednesday, October 4, 2023	Approved
Vim Tux (Install) 9.0.1943	524	Wednesday, September 27, 2023	Approved
Vim Tux (Install) 9.0.1927	616	Friday, September 22, 2023	Approved
Vim Tux (Install) 9.0.1907	83	Tuesday, September 19, 2023	Approved
Vim Tux (Install) 9.0.1901	193	Saturday, September 16, 2023	Approved
Vim Tux (Install) 9.0.1897	122	Wednesday, September 13, 2023	Approved
Vim Tux (Install) 9.0.1877	57	Thursday, September 7, 2023	Approved
Vim Tux (Install) 9.0.1872	80	Wednesday, September 6, 2023	Exempted
Vim Tux (Install) 9.0.0814	130	Saturday, October 22, 2022	Approved
Vim Tux (Install) 9.0.0806	70	Friday, October 21, 2022	Approved
Vim Tux (Install) 9.0.0797	94	Thursday, October 20, 2022	Approved
Vim Tux (Install) 9.0.0780	101	Tuesday, October 18, 2022	Approved
Vim Tux (Install) 9.0.0733	117	Thursday, October 13, 2022	Approved
Vim Tux (Install) 9.0.0715	89	Tuesday, October 11, 2022	Approved
Vim Tux (Install) 9.0.0682	143	Saturday, October 8, 2022	Approved
Vim Tux (Install) 9.0.656.20221005	98	Thursday, October 6, 2022	Approved
Vim Tux (Install) 9.0.0656	94	Wednesday, October 5, 2022	Approved
Vim Tux (Install) 8.2.3875	541	Thursday, December 23, 2021	Approved
Vim Tux (Install) 8.2.3836	161	Saturday, December 18, 2021	Approved
Vim Tux (Install) 8.2.3811	155	Wednesday, December 15, 2021	Approved
Vim Tux (Install) 8.2.3794	141	Tuesday, December 14, 2021	Approved
Vim Tux (Install) 8.2.3757	152	Wednesday, December 8, 2021	Approved
Vim Tux (Install) 8.2.3752	120	Tuesday, December 7, 2021	Approved
Vim Tux (Install) 8.2.3718	171	Friday, December 3, 2021	Approved
Vim Tux (Install) 8.2.3717	136	Thursday, December 2, 2021	Approved
Vim Tux (Install) 8.2.3701	105	Wednesday, December 1, 2021	Approved
Vim Tux (Install) 8.2.3692	102	Monday, November 29, 2021	Approved
Vim Tux (Install) 8.2.3671	191	Friday, November 26, 2021	Approved
Vim Tux (Install) 8.2.3659	160	Thursday, November 25, 2021	Approved
Vim Tux (Install) 8.2.3651	128	Tuesday, November 23, 2021	Approved
Vim Tux (Install) 8.2.3646	143	Tuesday, November 23, 2021	Approved
Vim Tux (Install) 8.2.3623	167	Saturday, November 20, 2021	Approved
Vim Tux (Install) 8.2.3608	143	Thursday, November 18, 2021	Approved
Vim Tux (Install) 8.2.3595	163	Tuesday, November 16, 2021	Approved
Vim Tux (Install) 8.2.3579	271	Friday, November 5, 2021	Approved
Vim Tux (Install) 8.2.3565	238	Wednesday, October 27, 2021	Approved
Vim Tux (Install) 8.2.3551	186	Friday, October 22, 2021	Approved
Vim Tux (Install) 8.2.3545	151	Thursday, October 21, 2021	Approved
Vim Tux (Install) 8.2.3532	136	Tuesday, October 19, 2021	Approved
Vim Tux (Install) 8.2.3513	188	Saturday, October 16, 2021	Approved
Vim Tux (Install) 8.2.3505	176	Thursday, October 14, 2021	Approved
Vim Tux (Install) 8.2.3493	166	Monday, October 11, 2021	Approved
Vim Tux (Install) 8.2.3486	158	Saturday, October 9, 2021	Approved
Vim Tux (Install) 8.2.3484	150	Thursday, October 7, 2021	Approved
Vim Tux (Install) 8.2.3478	117	Wednesday, October 6, 2021	Approved
Vim Tux (Install) 8.2.3469	124	Tuesday, October 5, 2021	Approved
Vim Tux (Install) 8.2.3458	252	Tuesday, September 28, 2021	Approved
Vim Tux (Install) 8.2.3455	184	Thursday, September 23, 2021	Approved
Vim Tux (Install) 8.2.3450	153	Tuesday, September 21, 2021	Approved
Vim Tux (Install) 8.2.3448	135	Sunday, September 19, 2021	Approved
Vim Tux (Install) 8.2.3434	163	Tuesday, September 14, 2021	Approved
Vim Tux (Install) 8.2.3416	233	Thursday, September 9, 2021	Approved
Vim Tux (Install) 8.2.3394	231	Thursday, September 2, 2021	Approved
Vim Tux (Install) 8.2.3391	126	Wednesday, September 1, 2021	Approved
Vim Tux (Install) 8.2.3376	208	Thursday, August 26, 2021	Approved
Vim Tux (Install) 8.2.3358	216	Friday, August 20, 2021	Approved
Vim Tux (Install) 8.2.3356	141	Wednesday, August 18, 2021	Approved
Vim Tux (Install) 8.2.3326	216	Wednesday, August 11, 2021	Approved
Vim Tux (Install) 8.2.3318	142	Monday, August 9, 2021	Approved
Vim Tux (Install) 8.2.3299	182	Friday, August 6, 2021	Approved
Vim Tux (Install) 8.2.3290	99	Thursday, August 5, 2021	Approved
Vim Tux (Install) 8.2.3281	162	Wednesday, August 4, 2021	Approved
Vim Tux (Install) 8.2.3273	137	Monday, August 2, 2021	Approved
Vim Tux (Install) 8.2.3269	128	Monday, August 2, 2021	Approved
Vim Tux (Install) 8.2.3263	88	Sunday, August 1, 2021	Approved
Vim Tux (Install) 8.2.3253	128	Saturday, July 31, 2021	Approved
Vim Tux (Install) 8.2.3242	141	Thursday, July 29, 2021	Approved
Vim Tux (Install) 8.2.3204	182	Friday, July 23, 2021	Approved
Vim Tux (Install) 8.2.3187	191	Tuesday, July 20, 2021	Approved
Vim Tux (Install) 8.2.3171	204	Friday, July 16, 2021	Approved
Vim Tux (Install) 8.2.3158	225	Wednesday, July 14, 2021	Approved
Vim Tux (Install) 8.2.3154	191	Monday, July 12, 2021	Approved
Vim Tux (Install) 8.2.3131	175	Friday, July 9, 2021	Approved
Vim Tux (Install) 8.2.3120	153	Thursday, July 8, 2021	Approved
Vim Tux (Install) 8.2.3113	120	Wednesday, July 7, 2021	Approved
Vim Tux (Install) 8.2.3107	179	Monday, July 5, 2021	Approved
Vim Tux (Install) 8.2.3095	144	Sunday, July 4, 2021	Approved
Vim Tux (Install) 8.2.3080	207	Thursday, July 1, 2021	Approved
Vim Tux (Install) 8.2.3075	128	Wednesday, June 30, 2021	Approved
Vim Tux (Install) 8.2.3066	161	Monday, June 28, 2021	Approved
Vim Tux (Install) 8.2.3055	145	Sunday, June 27, 2021	Approved
Vim Tux (Install) 8.2.3043	160	Thursday, June 24, 2021	Exempted
Vim Tux (Install) 8.2.3033	203	Tuesday, June 22, 2021	Approved
Vim Tux (Install) 8.2.3017	159	Friday, June 18, 2021	Exempted
Vim Tux (Install) 8.2.2832	218	Wednesday, May 5, 2021	Exempted
Vim Tux (Install) 8.2.2799	283	Thursday, April 22, 2021	Approved
Vim Tux (Install) 8.2.2794	134	Wednesday, April 21, 2021	Approved
Vim Tux (Install) 8.2.2763	243	Thursday, April 15, 2021	Approved
Vim Tux (Install) 8.2.2738	214	Friday, April 9, 2021	Approved
Vim Tux (Install) 8.2.2730	166	Wednesday, April 7, 2021	Approved
Vim Tux (Install) 8.2.2679	198	Wednesday, March 31, 2021	Approved
Vim Tux (Install) 8.2.2650	131	Friday, March 26, 2021	Approved
Vim Tux (Install) 8.2.2648	286	Wednesday, March 24, 2021	Approved
Vim Tux (Install) 8.2.2417	315	Thursday, January 28, 2021	Approved
Vim Tux (Install) 8.2.2129	605	Saturday, December 12, 2020	Approved
Vim Tux (Install) 8.2.1981	520	Saturday, November 14, 2020	Approved
Vim Tux (Install) 8.2.1955	415	Friday, November 6, 2020	Approved
Vim Tux (Install) 8.2.1905	369	Monday, October 26, 2020	Approved
Vim Tux (Install) 8.2.1883	322	Thursday, October 22, 2020	Approved
Vim Tux (Install) 8.2.1858	332	Sunday, October 18, 2020	Approved
Vim Tux (Install) 8.2.1801	383	Monday, October 5, 2020	Approved
Vim Tux (Install) 8.2.1651	522	Thursday, September 10, 2020	Approved
Vim Tux (Install) 8.2.1139	842	Monday, July 6, 2020	Approved
Vim Tux (Install) 8.2.1058	528	Friday, June 26, 2020	Approved
Vim Tux (Install) 8.2.960	453	Friday, June 12, 2020	Approved
Vim Tux (Install) 8.2.950	293	Thursday, June 11, 2020	Approved
Vim Tux (Install) 8.2.916	307	Sunday, June 7, 2020	Approved
Vim Tux (Install) 8.2.882	441	Tuesday, June 2, 2020	Approved
Vim Tux (Install) 8.2.855	216	Sunday, May 31, 2020	Approved
Vim Tux (Install) 8.2.834	247	Friday, May 29, 2020	Approved
Vim Tux (Install) 8.2.829	339	Wednesday, May 27, 2020	Approved
Vim Tux (Install) 8.2.821	303	Tuesday, May 26, 2020	Approved
Vim Tux (Install) 8.2.806	296	Friday, May 22, 2020	Approved
Vim Tux (Install) 8.2.803	204	Thursday, May 21, 2020	Approved
Vim Tux (Install) 8.2.750	358	Thursday, May 14, 2020	Approved
Vim Tux (Install) 8.2.647	445	Monday, April 27, 2020	Approved
Vim Tux (Install) 8.2.640	274	Sunday, April 26, 2020	Approved
Vim Tux (Install) 8.2.625	321	Friday, April 24, 2020	Approved
Vim Tux (Install) 8.2.612	299	Tuesday, April 21, 2020	Approved
Vim Tux (Install) 8.2.592	238	Saturday, April 18, 2020	Approved
Vim Tux (Install) 8.2.585	254	Friday, April 17, 2020	Approved
Vim Tux (Install) 8.2.577	269	Wednesday, April 15, 2020	Approved
Vim Tux (Install) 8.2.0357	699	Friday, March 6, 2020	Approved
Vim Tux (Install) 8.2.0324	390	Friday, February 28, 2020	Approved
Vim Tux (Install) 8.2.0313	315	Monday, February 24, 2020	Approved
Vim Tux (Install) 8.2.0294	260	Saturday, February 22, 2020	Approved
Vim Tux (Install) 8.2.0285	226	Friday, February 21, 2020	Approved
Vim Tux (Install) 8.2.0273	299	Tuesday, February 18, 2020	Approved
Vim Tux (Install) 8.2.0231	395	Sunday, February 9, 2020	Approved
Vim Tux (Install) 8.2.0184	388	Friday, January 31, 2020	Approved
Vim Tux (Install) 8.2.0164	293	Wednesday, January 29, 2020	Approved
Vim Tux (Install) 8.2.0140	329	Wednesday, January 22, 2020	Approved
Vim Tux (Install) 8.2.0129	347	Sunday, January 19, 2020	Approved
Vim Tux (Install) 8.2.0114	474	Tuesday, January 14, 2020	Approved
Vim Tux (Install) 8.2.0109	310	Friday, January 10, 2020	Approved
Vim Tux (Install) 8.2.0092	387	Tuesday, January 7, 2020	Approved
Vim Tux (Install) 8.2.0080	526	Friday, January 3, 2020	Approved
Vim Tux (Install) 8.1.2333	857	Friday, November 22, 2019	Approved
Vim Tux (Install) 8.1.2323	440	Thursday, November 21, 2019	Approved
Vim Tux (Install) 8.1.2311	529	Sunday, November 17, 2019	Approved
Vim Tux (Install) 8.1.2300	425	Thursday, November 14, 2019	Approved
Vim Tux (Install) 8.1.2237	633	Friday, November 1, 2019	Approved
Vim Tux (Install) 8.1.2204	664	Thursday, October 24, 2019	Approved
Vim Tux (Install) 8.1.2200	422	Wednesday, October 23, 2019	Approved
Vim Tux (Install) 8.1.2148	754	Monday, October 14, 2019	Approved
Vim Tux (Install) 8.1.2133	490	Friday, October 11, 2019	Approved
Vim Tux (Install) 8.1.2117	596	Sunday, October 6, 2019	Approved
Vim Tux (Install) 8.1.2108	459	Thursday, October 3, 2019	Approved
Vim Tux (Install) 8.1.2103	468	Tuesday, October 1, 2019	Approved
Vim Tux (Install) 8.1.2079	521	Friday, September 27, 2019	Approved
Vim Tux (Install) 8.1.2071	497	Wednesday, September 25, 2019	Approved
Vim Tux (Install) 8.1.2052	611	Thursday, September 19, 2019	Approved
Vim Tux (Install) 8.1.2019	676	Tuesday, September 10, 2019	Approved
Vim Tux (Install) 8.1.2004	488	Sunday, September 8, 2019	Approved
Vim Tux (Install) 8.1.1995	346	Saturday, September 7, 2019	Approved
Vim Tux (Install) 8.1.1986	455	Thursday, September 5, 2019	Approved
Vim Tux (Install) 8.1.1961	478	Monday, September 2, 2019	Approved
Vim Tux (Install) 8.1.1927	614	Monday, August 26, 2019	Approved
Vim Tux (Install) 8.1.1915	339	Saturday, August 24, 2019	Approved
Vim Tux (Install) 8.1.1906	388	Thursday, August 22, 2019	Approved
Vim Tux (Install) 8.1.1890	427	Tuesday, August 20, 2019	Approved
Vim Tux (Install) 8.1.1836	546	Sunday, August 11, 2019	Approved
Vim Tux (Install) 8.1.1744	737	Thursday, July 25, 2019	Approved
Vim Tux (Install) 8.1.1729	427	Tuesday, July 23, 2019	Approved
Vim Tux (Install) 8.1.1713	449	Friday, July 19, 2019	Approved
Vim Tux (Install) 8.1.1695	453	Tuesday, July 16, 2019	Approved
Vim Tux (Install) 8.1.1669	461	Saturday, July 13, 2019	Approved
Vim Tux (Install) 8.1.1655	549	Tuesday, July 9, 2019	Approved
Vim Tux (Install) 8.1.1631	449	Friday, July 5, 2019	Approved
Vim Tux (Install) 8.1.1601	575	Thursday, June 27, 2019	Approved
Vim Tux (Install) 8.1.1587	401	Tuesday, June 25, 2019	Approved
Vim Tux (Install) 8.1.1573	454	Thursday, June 20, 2019	Approved
Vim Tux (Install) 8.1.1566	520	Tuesday, June 18, 2019	Approved
Vim Tux (Install) 8.1.1557	333	Monday, June 17, 2019	Approved
Vim Tux (Install) 8.1.1536	339	Sunday, June 16, 2019	Approved
Vim Tux (Install) 8.1.1523	323	Friday, June 14, 2019	Approved
Vim Tux (Install) 8.1.1515	377	Tuesday, June 11, 2019	Approved
Vim Tux (Install) 8.1.1511	441	Monday, June 10, 2019	Approved
Vim Tux (Install) 8.1.1455	521	Monday, June 3, 2019	Approved
Vim Tux (Install) 8.1.1432	359	Friday, May 31, 2019	Approved
Vim Tux (Install) 8.1.1413	395	Tuesday, May 28, 2019	Approved
Vim Tux (Install) 8.1.1373	499	Friday, May 24, 2019	Approved
Vim Tux (Install) 8.1.1364	344	Thursday, May 23, 2019	Approved
Vim Tux (Install) 8.1.1353	509	Monday, May 20, 2019	Approved
Vim Tux (Install) 8.1.1333	471	Thursday, May 16, 2019	Approved
Vim Tux (Install) 8.1.1328	436	Monday, May 13, 2019	Approved
Vim Tux (Install) 8.1.1312	322	Saturday, May 11, 2019	Approved
Vim Tux (Install) 8.1.1298	392	Thursday, May 9, 2019	Approved
Vim Tux (Install) 8.1.1286	409	Tuesday, May 7, 2019	Approved
Vim Tux (Install) 8.1.1229	554	Monday, April 29, 2019	Approved
Vim Tux (Install) 8.1.1183	430	Thursday, April 18, 2019	Approved
Vim Tux (Install) 8.1.1173	429	Monday, April 15, 2019	Approved
Vim Tux (Install) 8.1.1165	317	Sunday, April 14, 2019	Approved
Vim Tux (Install) 8.1.1140	491	Tuesday, April 9, 2019	Approved
Vim Tux (Install) 8.1.1136	390	Monday, April 8, 2019	Approved
Vim Tux (Install) 8.1.1124	324	Sunday, April 7, 2019	Approved
Vim Tux (Install) 8.1.1116	371	Thursday, April 4, 2019	Approved
Vim Tux (Install) 8.1.1103	352	Thursday, April 4, 2019	Approved
Vim Tux (Install) 8.1.1097	314	Monday, April 1, 2019	Approved
Vim Tux (Install) 8.1.1073	464	Saturday, March 30, 2019	Approved
Vim Tux (Install) 8.1.1057	418	Thursday, March 28, 2019	Approved
Vim Tux (Install) 8.1.1045	206	Sunday, March 24, 2019	Approved
Vim Tux (Install) 8.1.1032	181	Friday, March 22, 2019	Approved
Vim Tux (Install) 8.1.1027	527	Thursday, March 21, 2019	Approved
Vim Tux (Install) 8.1.1017	360	Tuesday, March 19, 2019	Approved
Vim Tux (Install) 8.1.1004	621	Monday, March 11, 2019	Approved
Vim Tux (Install) 8.1.998	417	Friday, March 8, 2019	Approved
Vim Tux (Install) 8.1.990	558	Sunday, March 3, 2019	Approved
Vim Tux (Install) 8.1.984	438	Thursday, February 28, 2019	Approved
Vim Tux (Install) 8.1.978	463	Saturday, February 23, 2019	Approved
Vim Tux (Install) 8.1.966	372	Friday, February 22, 2019	Approved
Vim Tux (Install) 8.1.947	456	Tuesday, February 19, 2019	Approved
Vim Tux (Install) 8.1.934	333	Sunday, February 17, 2019	Approved
Vim Tux (Install) 8.1.926	343	Saturday, February 16, 2019	Approved
Vim Tux (Install) 8.1.909	356	Thursday, February 14, 2019	Approved
Vim Tux (Install) 8.1.895	384	Tuesday, February 12, 2019	Approved
Vim Tux (Install) 8.1.0885	359	Sunday, February 10, 2019	Approved
Vim Tux (Install) 8.1.0877	221	Thursday, February 7, 2019	Approved
Vim Tux (Install) 8.1.0871	441	Monday, February 4, 2019	Approved
Vim Tux (Install) 8.1.0868	311	Sunday, February 3, 2019	Approved
Vim Tux (Install) 8.1.0865	319	Saturday, February 2, 2019	Approved
Vim Tux (Install) 8.1.0842	314	Thursday, January 31, 2019	Approved
Vim Tux (Install) 8.1.0837	399	Monday, January 28, 2019	Approved
Vim Tux (Install) 8.1.0814	378	Friday, January 25, 2019	Approved
Vim Tux (Install) 8.1.0796	330	Thursday, January 24, 2019	Approved
Vim Tux (Install) 8.1.0788	361	Tuesday, January 22, 2019	Approved
Vim Tux (Install) 8.1.0712	508	Thursday, January 10, 2019	Approved
Vim Tux (Install) 8.1.0700	378	Tuesday, January 8, 2019	Approved
Vim Tux (Install) 8.1.0690	447	Saturday, January 5, 2019	Approved
Vim Tux (Install) 8.1.0681	322	Thursday, January 3, 2019	Approved
Vim Tux (Install) 8.1.0674	325	Wednesday, January 2, 2019	Approved
Vim Tux (Install) 8.1.0647	376	Friday, December 28, 2018	Approved
Vim Tux (Install) 8.1.0635	341	Wednesday, December 26, 2018	Approved
Vim Tux (Install) 8.1.0630	274	Tuesday, December 25, 2018	Approved
Vim Tux (Install) 8.1.0629	292	Monday, December 24, 2018	Approved
Vim Tux (Install) 8.1.0622	249	Sunday, December 23, 2018	Approved
Vim Tux (Install) 8.1.0617	371	Saturday, December 22, 2018	Approved
Vim Tux (Install) 8.1.0594	505	Sunday, December 16, 2018	Approved
Vim Tux (Install) 8.1.0577	367	Thursday, December 13, 2018	Approved
Vim Tux (Install) 8.1.0551	612	Friday, November 30, 2018	Approved
Vim Tux (Install) 8.1.0547	467	Monday, November 26, 2018	Approved
Vim Tux (Install) 8.1.0536	452	Tuesday, November 20, 2018	Approved
Vim Tux (Install) 8.1.0524	477	Tuesday, November 13, 2018	Approved
Vim Tux (Install) 8.1.0513	382	Thursday, November 8, 2018	Approved
Vim Tux (Install) 8.1.0509	409	Sunday, November 4, 2018	Approved
Vim Tux (Install) 8.1.0498	478	Sunday, October 28, 2018	Approved
Vim Tux (Install) 8.1.0489	415	Monday, October 22, 2018	Approved
Vim Tux (Install) 8.1.0474	499	Monday, October 15, 2018	Approved
Vim Tux (Install) 8.1.0470	394	Friday, October 12, 2018	Approved
Vim Tux (Install) 8.1.0451	477	Friday, October 5, 2018	Approved
Vim Tux (Install) 8.1.0442	452	Monday, October 1, 2018	Approved
Vim Tux (Install) 8.1.0436	438	Thursday, September 27, 2018	Approved
Vim Tux (Install) 8.1.0425	479	Saturday, September 22, 2018	Approved
Vim Tux (Install) 8.1.0408	329	Thursday, September 20, 2018	Approved
Vim Tux (Install) 8.1.0401	317	Tuesday, September 18, 2018	Approved
Vim Tux (Install) 8.1.0385	467	Friday, September 14, 2018	Approved
Vim Tux (Install) 8.1.0371	343	Thursday, September 13, 2018	Approved
Vim Tux (Install) 8.1.0362	395	Tuesday, September 11, 2018	Approved
Vim Tux (Install) 8.1.0354	365	Sunday, September 9, 2018	Approved
Vim Tux (Install) 8.1.0347	378	Thursday, September 6, 2018	Approved
Vim Tux (Install) 8.1.0342	374	Sunday, September 2, 2018	Approved
Vim Tux (Install) 8.1.0332	400	Thursday, August 30, 2018	Approved
Vim Tux (Install) 8.1.0327	410	Sunday, August 26, 2018	Approved
Vim Tux (Install) 8.1.0318	343	Thursday, August 23, 2018	Approved
Vim Tux (Install) 8.1.0301	250	Tuesday, August 21, 2018	Approved
Vim Tux (Install) 8.1.0297	385	Monday, August 20, 2018	Approved
Vim Tux (Install) 8.1.0288	386	Thursday, August 16, 2018	Approved
Vim Tux (Install) 8.1.0278	389	Monday, August 13, 2018	Approved
Vim Tux (Install) 8.1.0271	308	Sunday, August 12, 2018	Approved
Vim Tux (Install) 8.1.0259	404	Friday, August 10, 2018	Approved
Vim Tux (Install) 8.1.0239	441	Sunday, August 5, 2018	Approved
Vim Tux (Install) 8.1.0229	411	Tuesday, July 31, 2018	Approved
Vim Tux (Install) 8.1.0221	352	Sunday, July 29, 2018	Approved
Vim Tux (Install) 8.1.0210	370	Thursday, July 26, 2018	Approved
Vim Tux (Install) 8.1.0207	344	Tuesday, July 24, 2018	Approved
Vim Tux (Install) 8.1.0203	380	Monday, July 23, 2018	Approved
Vim Tux (Install) 8.1.0199	382	Saturday, July 21, 2018	Approved
Vim Tux (Install) 8.1.0196	336	Friday, July 20, 2018	Approved
Vim Tux (Install) 8.1.0191	398	Tuesday, July 17, 2018	Approved
Vim Tux (Install) 8.1.0186	349	Sunday, July 15, 2018	Approved
Vim Tux (Install) 8.1.0173	455	Tuesday, July 10, 2018	Approved
Vim Tux (Install) 8.1.0153	440	Friday, July 6, 2018	Approved
Vim Tux (Install) 8.1.0138	388	Tuesday, July 3, 2018	Approved
Vim Tux (Install) 8.1.0133	507	Sunday, July 1, 2018	Approved
Vim Tux (Install) 8.1.0126	391	Friday, June 29, 2018	Approved
Vim Tux (Install) 8.1.0105	420	Sunday, June 24, 2018	Approved
Vim Tux (Install) 8.1.0054	619	Thursday, June 14, 2018	Approved
Vim Tux (Install) 8.1.0034	666	Tuesday, June 5, 2018	Approved
Vim Tux (Install) 8.1.0022	522	Friday, May 25, 2018	Approved
Vim Tux (Install) 8.1.0013	447	Tuesday, May 22, 2018	Approved
Vim Tux (Install) 8.1.0009	349	Monday, May 21, 2018	Approved
Vim Tux (Install) 8.1.0004	308	Sunday, May 20, 2018	Approved
Vim Tux (Install) 8.1.0000	366	Saturday, May 19, 2018	Approved
Vim Tux (Install) 8.0.1848	367	Thursday, May 17, 2018	Approved
Vim Tux (Install) 8.0.1831	425	Monday, May 14, 2018	Approved
Vim Tux (Install) 8.0.1820	375	Sunday, May 13, 2018	Approved
Vim Tux (Install) 8.0.1806	436	Thursday, May 10, 2018	Approved
Vim Tux (Install) 8.0.1799	434	Monday, May 7, 2018	Approved
Vim Tux (Install) 8.0.1794	311	Sunday, May 6, 2018	Approved
Vim Tux (Install) 8.0.1790	350	Friday, May 4, 2018	Approved
Vim Tux (Install) 8.0.1788	408	Thursday, May 3, 2018	Approved
Vim Tux (Install) 8.0.1774	443	Monday, April 30, 2018	Approved
Vim Tux (Install) 8.0.1765	473	Thursday, April 26, 2018	Approved
Vim Tux (Install) 8.0.1748	396	Sunday, April 22, 2018	Approved
Vim Tux (Install) 8.0.1736	358	Friday, April 20, 2018	Approved
Vim Tux (Install) 8.0.1727	382	Wednesday, April 18, 2018	Approved
Vim Tux (Install) 8.0.1705	428	Saturday, April 14, 2018	Approved
Vim Tux (Install) 8.0.1679	482	Monday, April 9, 2018	Approved
Vim Tux (Install) 8.0.1664	383	Saturday, April 7, 2018	Approved
Vim Tux (Install) 8.0.1655	469	Saturday, March 31, 2018	Approved
Vim Tux (Install) 8.0.1638	578	Sunday, March 25, 2018	Approved
Vim Tux (Install) 8.0.1626	481	Thursday, March 22, 2018	Approved
Vim Tux (Install) 8.0.1612	473	Saturday, March 17, 2018	Approved
Vim Tux (Install) 8.0.1601	493	Tuesday, March 13, 2018	Approved
Vim Tux (Install) 8.0.1591	467	Friday, March 9, 2018	Approved
Vim Tux (Install) 8.0.1563	491	Sunday, March 4, 2018	Approved
Vim Tux (Install) 8.0.1553	355	Friday, March 2, 2018	Approved
Vim Tux (Install) 8.0.1532	548	Sunday, February 25, 2018	Approved
Vim Tux (Install) 8.0.1504	662	Thursday, February 15, 2018	Approved
Vim Tux (Install) 8.0.1473	516	Thursday, February 8, 2018	Approved
Vim Tux (Install) 8.0.1451	493	Saturday, February 3, 2018	Approved
Vim Tux (Install) 8.0.1438	453	Tuesday, January 30, 2018	Approved
Vim Tux (Install) 8.0.1431	494	Saturday, January 27, 2018	Approved
Vim Tux (Install) 8.0.1428	705	Thursday, January 4, 2018	Approved
Vim Tux (Install) 8.0.1422	475	Saturday, December 30, 2017	Approved
Vim Tux (Install) 8.0.1390	581	Sunday, December 17, 2017	Approved
Vim Tux (Install) 8.0.1379	438	Thursday, December 14, 2017	Approved
Vim Tux (Install) 8.0.1376	496	Thursday, December 7, 2017	Approved
Vim Tux (Install) 8.0.1358	573	Friday, December 1, 2017	Approved
Vim Tux (Install) 8.0.1330	565	Thursday, November 23, 2017	Approved
Vim Tux (Install) 8.0.1311	472	Monday, November 20, 2017	Approved
Vim Tux (Install) 8.0.1305	467	Saturday, November 18, 2017	Approved
Vim Tux (Install) 8.0.1272	589	Thursday, November 9, 2017	Approved
Vim Tux (Install) 8.0.1257	507	Sunday, November 5, 2017	Approved
Vim Tux (Install) 8.0.1203	654	Wednesday, October 18, 2017	Approved
Vim Tux (Install) 8.0.1157	679	Friday, September 29, 2017	Approved
Vim Tux (Install) 8.0.1088	685	Monday, September 11, 2017	Approved
Vim Tux (Install) 8.0.1010	608	Tuesday, August 29, 2017	Approved
Vim Tux (Install) 8.0.0737	771	Thursday, July 20, 2017	Approved
Vim Tux (Install) 8.0.0642	737	Sunday, June 18, 2017	Approved
Vim Tux (Install) 8.0.0584	917	Wednesday, April 26, 2017	Approved
Vim Tux (Install) 8.0.0575	566	Friday, April 21, 2017	Approved
Vim Tux (Install) 8.0.0430	917	Thursday, March 9, 2017	Approved
Vim Tux (Install) 8.0.0320	804	Friday, February 10, 2017	Approved
Vim Tux (Install) 8.0.0206	762	Friday, January 20, 2017	Approved
Vim Tux (Install) 8.0.0194	465	Tuesday, January 17, 2017	Approved
Vim Tux (Install) 8.0.0123	858	Friday, December 9, 2016	Approved
Vim Tux (Install) 8.0.0117	510	Friday, December 2, 2016	Approved
Vim Tux (Install) 8.0.0066	703	Thursday, November 10, 2016	Approved
Vim Tux (Install) 8.0.0051	651	Friday, October 28, 2016	Approved
Vim Tux (Install) 8.0.0045	532	Friday, October 21, 2016	Approved
Vim Tux (Install) 8.0.0017	608	Wednesday, September 28, 2016	Approved
Vim Tux (Install) 8.0.005	676	Friday, September 16, 2016	Approved
Vim Tux (Install) 7.4.2222	744	Thursday, August 18, 2016	Approved
Vim Tux (Install) 7.4.2180	373	Tuesday, August 9, 2016	Approved
Vim Tux (Install) 7.4.2153	402	Friday, August 5, 2016	Approved
Vim Tux (Install) 7.4.2089	605	Friday, July 22, 2016	Approved
Vim Tux (Install) 7.4.2034	366	Friday, July 15, 2016	Approved
Vim Tux (Install) 7.4.1998	377	Friday, July 8, 2016	Approved
Vim Tux (Install) 7.4.1987	411	Sunday, July 3, 2016	Approved
Vim Tux (Install) 7.4.1949	404	Thursday, June 23, 2016	Approved
Vim Tux (Install) 7.4.1913	416	Friday, June 10, 2016	Approved
Vim Tux (Install) 7.4.1905	462	Thursday, June 9, 2016	Approved
Vim Tux (Install) 7.4.1901	423	Tuesday, June 7, 2016	Approved
Vim Tux (Install) 7.4.1862	392	Thursday, June 2, 2016	Approved
Vim Tux (Install) 7.4.1856	386	Monday, May 30, 2016	Approved
Vim Tux (Install) 7.4.1848	378	Friday, May 27, 2016	Approved
Vim Tux (Install) 7.4.1842	368	Thursday, May 26, 2016	Approved
Vim Tux (Install) 7.4.1832	375	Thursday, May 19, 2016	Approved
Vim Tux (Install) 7.4.1829	371	Thursday, May 12, 2016	Approved
Vim Tux (Install) 7.4.1824	393	Monday, May 9, 2016	Approved

2023 Vim Team

Release Notes

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

Dependencies

- vcredist2015 (≥ 14.0.24215.20170201)
- chocolatey-core.extension (≥ 1.1.0)

Discussion for the Vim Tux (Install) Package

Ground Rules:

This discussion is only about Vim Tux (Install) and the Vim Tux (Install) 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 (Install), 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

153,356

12

04 Nov 2024

Vim Tux (Install)

Vim Tux (Install) 9.1.837

Some Checks Have Failed or Are Not Yet Complete

Deployment Method: Individual Install, Upgrade, & Uninstall

Deployment Method:

1. Enter Your Internal Repository Url

2. Setup Your Environment

1. Ensure you are set for organizational deployment

2. Get the package into your environment

3. Copy Your Script

4. If applicable - Chocolatey configuration/installation

Package Parameters

Notes

Antivirus Detections

Ground Rules: