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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

- name: Install and Configure Chocolatey
  hosts: all

## 2. TOP LEVEL VARIABLES ##
  vars:

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

chocolatey_feature 'useBackgroundService' do
  action :enable
end

chocolatey_feature 'useBackgroundServiceWithNonAdministratorsOnly' do
  action :enable
end

chocolatey_feature 'allowBackgroundServiceUninstallsFromUserInstallsOnly' do
  action :enable
end

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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


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

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

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

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

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


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


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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Need Help? View our docs or file an issue.

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

Current Version	New Version

Downloads:

140,108

Downloads of v 9.0.0846:

34

Last Update:

10 Nov 2022

Package Maintainer(s):

Pauby

Software Author(s):

Build: TuxProject.de
Developer: vim team

Tags:

vim-tux vim editor tux admin

Vim Tux (Install)

Downloads:

140,108

Downloads of v 9.0.0846:

Maintainer(s):

Pauby

Software Author(s):

Build: TuxProject.de
Developer: vim team

Tags:

vim-tux vim editor tux admin

Vim Tux (Install)

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Hide Checks

Validation Testing Passed

Verification Testing Failed

Details

Scan Testing Pending

NOTE

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

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

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

WARNING

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

WARNING

This package was rejected on 15 Dec 2022. The reviewer chocolatey-ops has listed the following reason(s):

LinkSatonaka (maintainer) on 10 Nov 2022 00:08:09 +00:00:

User 'LinkSatonaka' (maintainer) submitted package.

chocolatey-ops (reviewer) on 10 Nov 2022 00:41:37 +00:00:

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

Guidelines

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

Package contains dependencies with no specified version. You should at least specify a minimum version of a dependency. More...

Suggestions

Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.

As per the packaging guidelines icons should be either a png or svg file. More...

Notes

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

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

chocolatey-ops (reviewer) on 10 Nov 2022 02:19:57 +00:00:

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

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

chocolatey-ops (reviewer) on 30 Nov 2022 00:44:55 +00:00:

We've found vim-tux.install v9.0.0846 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.

Take action:

Log in to the site and respond to the review comments.
Resubmit fixes for this version.
If the package version is failing automated checks, you can self-reject the package.

If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.

Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.

chocolatey-ops (reviewer) on 15 Dec 2022 00:47:30 +00:00:

Unfortunately there has not been progress to move vim-tux.install v9.0.0846 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.

Status Change - Changed status of package from 'submitted' to 'rejected'.

Description

Package Parameters

The following package parameters can be set:

/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).

Please visit the official site at https://tuxproject.de/projects/vim/ for more information.
Build provided by TuxProject.de - consider donating to help support their server costs.

Files

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:

  checksumType: sha256
  checksum32: F6390F973D967B0C8E5D05D1FCB49FBADC25D8395B6172DD5BDEB1025539D3C7
  checksum64: A836B4318ECA6E17D2855AFAFA0BDF5AF6C3FA16D52545A56F93DFF8EA319D67

4. The install.exe and the uninstall.exe have been pulled from vim.org's version 90 release.
  
  checksumType: sha256
  install: 683364d52c6a922d1bb62ee799eacb05a40a820d5065ab9144095eb2cada749b
  uninstall: 2312a408505fe9fbe45779cdb49199f1bcd14cadb2b70a11cb6ffdd6ec852330

The file 'LICENSE.txt' has been obtained from <https://github.com/vim/vim/blob/master/runtime/doc/uganda.txt>

tools\uninstall

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\LICENSE.txt

*uganda.txt*    For Vim version 9.0.  Last change: 2022 Mar 02


		  VIM REFERENCE MANUAL    by Bram Moolenaar


			*uganda* *Uganda* *copying* *copyright* *license*
SUMMARY
								*iccf* *ICCF*
Vim is Charityware.  You can use and copy it as much as you like, but you are
encouraged to make a donation for needy children in Uganda.  Please see |kcc|
below or visit the ICCF web site, available at these URLs:

	https://iccf-holland.org/
	https://www.vim.org/iccf/
	https://www.iccf.nl/

You can also sponsor the development of Vim.  Vim sponsors can vote for
features.  See |sponsor|.  The money goes to Uganda anyway.

The Open Publication License applies to the Vim documentation, see
|manual-copyright|.

=== begin of license ===

VIM LICENSE

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

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

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

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

=== end of license ===

Note:

- If you are happy with Vim, please express that by reading the rest of this
  file and consider helping needy children in Uganda.

- If you want to support further Vim development consider becoming a
  |sponsor|.  The money goes to Uganda anyway.

- According to Richard Stallman the Vim license is GNU GPL compatible.
  A few minor changes have been made since he checked it, but that should not
  make a difference.

- If you link Vim with a library that goes under the GNU GPL, this limits
  further distribution to the GNU GPL.  Also when you didn't actually change
  anything in Vim.

- Once a change is included that goes under the GNU GPL, this forces all
  further changes to also be made under the GNU GPL or a compatible license.

- If you distribute a modified version of Vim, you can include your name and
  contact information with the "--with-modified-by" configure argument or the
  MODIFIED_BY define.

==============================================================================
Kibaale Children's Centre		*kcc* *Kibaale*  *charity*

Kibaale Children's Centre (KCC) is located in Kibaale, a small town in the
south of Uganda, near Tanzania, in East Africa.  The area is known as Rakai
District.  The population is mostly farmers.  Although people are poor, there
usually is enough food.  But this district is suffering from AIDS more than
any other part of the world.  Some say that it started there.  Estimations are
that in the past 10 to 30% of the Ugandans are infected with HIV.  Because
parents die, there are many orphans.  In this district about 60,000 children
have lost one or both parents, out of a population of 350,000.  Although AIDS
is now mostly under control, the problems are still continuing.

The children need a lot of help.  The KCC is working hard to provide the needy
with food, medical care and education.  Food and medical care to keep them
healthy now, and education so that they can take care of themselves in the
future.  KCC works on a Christian base, but help is given to children of any
religion.

The key to solving the problems in this area is education.  This has been
neglected in the past years with president Idi Amin and the following civil
wars.  Now that the government is stable again, the children and parents have
to learn how to take care of themselves and how to avoid infections.  There is
also help for people who are ill and hungry, but the primary goal is to
prevent people from getting ill and to teach them how to grow healthy food.

Most of the orphans are living in an extended family.  An uncle or older
sister is taking care of them.  Because these families are big and the income
(if any) is low, a child is lucky if it gets healthy food.  Clothes, medical
care and schooling is beyond its reach.  To help these needy children, a
sponsorship program was put into place.  A child can be financially adopted.
For a few dollars a month KCC sees to it that the child gets indispensable
items, is healthy, goes to school and KCC takes care of anything else that
needs to be done for the child and the family that supports it.

Besides helping the child directly, the environment where the child grows up
needs to be improved.  KCC helps schools to improve their teaching methods.
There is a demonstration school at the centre and teacher trainings are given.
Health workers are being trained, hygiene education is carried out and
households are stimulated to build a proper latrine.  I helped setting up a
production site for cement slabs.  These are used to build a good latrine.
They are sold below cost price.

There is a clinic at the project, which provides children and their family
medical help.  Since 2020 a maternity ward was added and 24/7 service is
available.  When needed, transport to a hospital is offered.  Immunization
programs are carried out and help is provided when an epidemic is breaking out
(measles and cholera have been a problem).
							*donate*
Summer 1994 to summer 1995 I spent a whole year at the centre, working as a
volunteer.  I have helped to expand the centre and worked in the area of water
and sanitation.  I learned that the help that the KCC provides really helps.
When I came back to Holland, I wanted to continue supporting KCC.  To do this
I'm raising funds and organizing the sponsorship program.  Please consider one
of these possibilities:

1.  Sponsor a child in primary school: 17 euro a month (or more).
2.  Sponsor a child in secondary school: 25 euro a month (or more).
3.  Sponsor the clinic: Any amount a month or quarter
4.  A one-time donation

Compared with other organizations that do child sponsorship the amounts are
very low.  This is because the money goes directly to the centre.  Less than
5% is used for administration.  This is possible because this is a small
organization that works with volunteers.  If you would like to sponsor a
child, you should have the intention to do this for at least one year.

How do you know that the money will be spent right?  First of all you have my
personal guarantee as the author of Vim.  I trust the people that are working
at the centre, I know them personally.  Furthermore, the centre has been
co-sponsored and inspected by World Vision, Save the Children Fund and is now
under the supervision of Pacific Academy Outreach Society.  The centre is
visited about once a year to check the progress (at our own cost).  I have
visited the centre myself many times, starting in 1993.  The visit reports are
on the ICCF web site.

If you have any further questions, send me e-mail: <[email protected]>.

The address of the centre is:
			Kibaale Children's Centre
			p.o. box 1658
			Masaka, Uganda, East Africa

Sending money:						*iccf-donations*

Check the ICCF web site for the latest information!  See |iccf| for the URL.


USA:		The methods mentioned below can be used.
		If you must send a check send it to our Canadian partner:
		https://www.kuwasha.net/

Canada:		Contact Kuwasha in Surrey, Canada.  They take care of the
		Canadian sponsors for the children in Kibaale.  Kuwasha
		forwards 100% of the money to the project in Uganda.  You can
		send them a one time donation directly.
		Please send me a note so that I know what has been donated
		because of Vim.  Look on their site for information about
		sponsorship: https://www.kuwasha.net/
		If you make a donation to Kuwasha you will receive a tax
		receipt which can be submitted with your tax return.

Holland:	Transfer to the account of "Stichting ICCF Holland" in
		Amersfoort.  This will allow for tax deduction if you live in
		Holland.  ING bank, IBAN: NL95 INGB 0004 5487 74

Germany:	It is possible to make donations that allow for a tax return.
		Check the ICCF web site for the latest information:
			https://iccf-holland.org/germany.html

Europe:		Use a bank transfer if possible.  See "Others" below for the
		swift code and IBAN number.
		Any other method should work.  Ask for information about
		sponsorship.

Credit Card:	You can use PayPal to send money with a Credit card.  This is
		the most widely used Internet based payment system.  It's
		really simple to use.  Use this link to find more info:
		    https://www.paypal.com/en_US/mrb/pal=XAC62PML3GF8Q
		The e-mail address for sending the money to is:
		    [email protected]

Others:		Transfer to this account if possible:
		    ING bank: 	IBAN: NL95 INGB 0004 5487 74
				Swift code: INGBNL2A
		    under the name "stichting ICCF Holland", Amersfoort
		Checks are not accepted.


 vim:tw=78:ts=8:noet:ft=help:norl:

tools\install

tools\complete-x86_x32.exe

md5: 57822AA0DB78FC491128DA08461CFBF0 | sha1: 192623253D5C27FB74E10F4782F5E70E91EB50E9 | sha256: F6390F973D967B0C8E5D05D1FCB49FBADC25D8395B6172DD5BDEB1025539D3C7 | sha512: A0EE23477D6BBE183A01BEB11F7F87F47E9B056402FE0E73D1D04459F05C359D0C7E08CA44CE11600B6CE67FB683A78347D7B3979FE7C0D8B3D37C78DD797BE7

tools\complete-x64_x64.exe

md5: 30DD9607AAA66E8B67A1F9E95B83F856 | sha1: 06E278826E2D3828C0B830F883F562F0A7331FE1 | sha256: A836B4318ECA6E17D2855AFAFA0BDF5AF6C3FA16D52545A56F93DFF8EA319D67 | sha512: C7518C284394E70F6598DEC49836AA506CDEB9854ECCA574ADC4423065CA5570DE4D83B9EBBCF48B04CBA32F4CB77B9F68D2082FA608A34DA37A72486D2849F3

tools\chocolateyuninstall.ps1

$packageName = 'vim-tux.install'
$versPath = 'vim90'
$destDir = Join-Path $ENV:ProgramFiles "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\chocolateyinstall.ps1

$ErrorActionPreference = 'Stop'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$versPath = 'vim90'
$destDir = Join-Path $ENV:ProgramFiles "Vim\$versPath"
if ($Env:ChocolateyPackageParameters -match '/InstallDir:\s*(.+)') {
	$destDir = $Matches[1]
	$destDir = $destDir -replace '^[''"]|[''"]$' # Strip quotations. Necessary?
	$destDir = $destDir -replace '[\/]$' # Remove any slashes from end of line
	if (-not ($destDir.EndsWith("$versPath"))) { $destDir = Join-Path $destDir "$versPath" } # installer will not run outside folder vim90
}

$pp = Get-PackageParameters

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

# Create batch files in C:\Windows by default
$createBatFiles = '-create-batfiles vim gvim evim view gview vimdiff gvimdiff'
if ($pp['NoCreateBatFiles'] -eq 'true') {
	Write-Debug 'Not installing batch files'
	$createBatFiles = $null
}

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

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

$packageArgs = @{
        packageName  = 'vim-tux.install'
        filetype     = 'exe'
        file         = gi $toolsDir\*_x32.exe
        file64       = gi $toolsDir\*_x64.exe
        silentArgs   = "-o`"$destDir`" -y"
        softwareName = 'vim*'
}

Install-ChocolateyPackage @packageArgs
Move-Item "$toolsDir\patch.exe.manifest" $destDir -Force -ea 0 # Supplied manifest fixes useless UAC request
(Get-Item $destdir\patch.exe).LastWriteTime = (Get-Date) # exe must be newer than manifest
# Run vim's installer
Move-Item "$toolsDir\install" "$destDir\install.exe" -Force -ea 0 # vim-tux removed the installer, just in time for Defender to stop flagging it
Move-Item "$toolsDir\uninstall" "$destDir\uninstall.exe" -Force -ea 0 # vim-tux removed the uninstaller, just in time for Defender to stop flagging it
Start-ChocolateyProcessAsAdmin "$installArgs" "$destDir\install.exe" -validExitCodes '0'
Remove-Item -Force -ea 0 "$toolsDir\*_x32.exe","$toolsDir\*_x64.exe"
Write-Host 'Build provided by TuxProject.de - consider donating to help support their server costs.'

Virus Scan Results

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

Version History

Version	Downloads	Last Updated	Status
Vim Tux (Install) 9.1.336	22	Tuesday, April 16, 2024	Approved
Vim Tux (Install) 9.1.330	21	Monday, April 15, 2024	Approved
Vim Tux (Install) 9.1.296	47	Thursday, April 11, 2024	Approved
Vim Tux (Install) 9.1.193	99	Friday, March 22, 2024	Approved
Vim Tux (Install) 9.1.186	40	Tuesday, March 19, 2024	Approved
Vim Tux (Install) 9.1.181	36	Friday, March 15, 2024	Approved
Vim Tux (Install) 9.1.149	10	Tuesday, March 5, 2024	Waiting for Maintainer
Vim Tux (Install) 9.1.146	12	Sunday, March 3, 2024	Waiting for Maintainer
Vim Tux (Install) 9.1.113	164	Friday, February 16, 2024	Approved
Vim Tux (Install) 9.1.67	120	Friday, February 2, 2024	Approved
Vim Tux (Install) 9.0.2181	181	Thursday, December 21, 2023	Approved
Vim Tux (Install) 9.0.2167	56	Friday, December 15, 2023	Approved
Vim Tux (Install) 9.0.2155	77	Saturday, December 9, 2023	Approved
Vim Tux (Install) 9.0.2146	65	Tuesday, December 5, 2023	Approved
Vim Tux (Install) 9.0.2134	63	Wednesday, November 29, 2023	Approved
Vim Tux (Install) 9.0.2122	70	Friday, November 24, 2023	Approved
Vim Tux (Install) 9.0.2120	45	Wednesday, November 22, 2023	Approved
Vim Tux (Install) 9.0.2103	89	Tuesday, November 14, 2023	Approved
Vim Tux (Install) 9.0.2095	69	Friday, November 10, 2023	Approved
Vim Tux (Install) 9.0.2092	60	Tuesday, November 7, 2023	Approved
Vim Tux (Install) 9.0.2081	65	Wednesday, November 1, 2023	Approved
Vim Tux (Install) 9.0.2077	60	Saturday, October 28, 2023	Approved
Vim Tux (Install) 9.0.2067	66	Friday, October 27, 2023	Approved
Vim Tux (Install) 9.0.2063	71	Tuesday, October 24, 2023	Approved
Vim Tux (Install) 9.0.2053	91	Friday, October 20, 2023	Approved
Vim Tux (Install) 9.0.2050	31	Thursday, October 19, 2023	Approved
Vim Tux (Install) 9.0.2048	42	Thursday, October 19, 2023	Approved
Vim Tux (Install) 9.0.2043	43	Wednesday, October 18, 2023	Approved
Vim Tux (Install) 9.0.2034	58	Tuesday, October 17, 2023	Approved
Vim Tux (Install) 9.0.2009	83	Tuesday, October 10, 2023	Approved
Vim Tux (Install) 9.0.1976	54	Wednesday, October 4, 2023	Approved
Vim Tux (Install) 9.0.1943	504	Wednesday, September 27, 2023	Approved
Vim Tux (Install) 9.0.1927	596	Friday, September 22, 2023	Approved
Vim Tux (Install) 9.0.1907	63	Tuesday, September 19, 2023	Approved
Vim Tux (Install) 9.0.1901	178	Saturday, September 16, 2023	Approved
Vim Tux (Install) 9.0.1897	99	Wednesday, September 13, 2023	Approved
Vim Tux (Install) 9.0.1877	34	Thursday, September 7, 2023	Approved
Vim Tux (Install) 9.0.1872	58	Wednesday, September 6, 2023	Exempted
Vim Tux (Install) 9.0.0814	107	Saturday, October 22, 2022	Approved
Vim Tux (Install) 9.0.0806	53	Friday, October 21, 2022	Approved
Vim Tux (Install) 9.0.0797	68	Thursday, October 20, 2022	Approved
Vim Tux (Install) 9.0.0780	81	Tuesday, October 18, 2022	Approved
Vim Tux (Install) 9.0.0733	99	Thursday, October 13, 2022	Approved
Vim Tux (Install) 9.0.0715	72	Tuesday, October 11, 2022	Approved
Vim Tux (Install) 9.0.0682	120	Saturday, October 8, 2022	Approved
Vim Tux (Install) 9.0.656.20221005	73	Thursday, October 6, 2022	Approved
Vim Tux (Install) 9.0.0656	72	Wednesday, October 5, 2022	Approved
Vim Tux (Install) 8.2.3875	516	Thursday, December 23, 2021	Approved
Vim Tux (Install) 8.2.3836	137	Saturday, December 18, 2021	Approved
Vim Tux (Install) 8.2.3811	138	Wednesday, December 15, 2021	Approved
Vim Tux (Install) 8.2.3794	124	Tuesday, December 14, 2021	Approved
Vim Tux (Install) 8.2.3757	136	Wednesday, December 8, 2021	Approved
Vim Tux (Install) 8.2.3752	103	Tuesday, December 7, 2021	Approved
Vim Tux (Install) 8.2.3718	150	Friday, December 3, 2021	Approved
Vim Tux (Install) 8.2.3717	121	Thursday, December 2, 2021	Approved
Vim Tux (Install) 8.2.3701	90	Wednesday, December 1, 2021	Approved
Vim Tux (Install) 8.2.3692	83	Monday, November 29, 2021	Approved
Vim Tux (Install) 8.2.3671	168	Friday, November 26, 2021	Approved
Vim Tux (Install) 8.2.3659	137	Thursday, November 25, 2021	Approved
Vim Tux (Install) 8.2.3651	109	Tuesday, November 23, 2021	Approved
Vim Tux (Install) 8.2.3646	116	Tuesday, November 23, 2021	Approved
Vim Tux (Install) 8.2.3623	148	Saturday, November 20, 2021	Approved
Vim Tux (Install) 8.2.3608	119	Thursday, November 18, 2021	Approved
Vim Tux (Install) 8.2.3595	149	Tuesday, November 16, 2021	Approved
Vim Tux (Install) 8.2.3579	247	Friday, November 5, 2021	Approved
Vim Tux (Install) 8.2.3565	215	Wednesday, October 27, 2021	Approved
Vim Tux (Install) 8.2.3551	171	Friday, October 22, 2021	Approved
Vim Tux (Install) 8.2.3545	129	Thursday, October 21, 2021	Approved
Vim Tux (Install) 8.2.3532	117	Tuesday, October 19, 2021	Approved
Vim Tux (Install) 8.2.3513	165	Saturday, October 16, 2021	Approved
Vim Tux (Install) 8.2.3505	155	Thursday, October 14, 2021	Approved
Vim Tux (Install) 8.2.3493	142	Monday, October 11, 2021	Approved
Vim Tux (Install) 8.2.3486	135	Saturday, October 9, 2021	Approved
Vim Tux (Install) 8.2.3484	133	Thursday, October 7, 2021	Approved
Vim Tux (Install) 8.2.3478	98	Wednesday, October 6, 2021	Approved
Vim Tux (Install) 8.2.3469	105	Tuesday, October 5, 2021	Approved
Vim Tux (Install) 8.2.3458	219	Tuesday, September 28, 2021	Approved
Vim Tux (Install) 8.2.3455	167	Thursday, September 23, 2021	Approved
Vim Tux (Install) 8.2.3450	134	Tuesday, September 21, 2021	Approved
Vim Tux (Install) 8.2.3448	111	Sunday, September 19, 2021	Approved
Vim Tux (Install) 8.2.3434	145	Tuesday, September 14, 2021	Approved
Vim Tux (Install) 8.2.3416	213	Thursday, September 9, 2021	Approved
Vim Tux (Install) 8.2.3394	205	Thursday, September 2, 2021	Approved
Vim Tux (Install) 8.2.3391	107	Wednesday, September 1, 2021	Approved
Vim Tux (Install) 8.2.3376	188	Thursday, August 26, 2021	Approved
Vim Tux (Install) 8.2.3358	202	Friday, August 20, 2021	Approved
Vim Tux (Install) 8.2.3356	118	Wednesday, August 18, 2021	Approved
Vim Tux (Install) 8.2.3326	196	Wednesday, August 11, 2021	Approved
Vim Tux (Install) 8.2.3318	125	Monday, August 9, 2021	Approved
Vim Tux (Install) 8.2.3299	160	Friday, August 6, 2021	Approved
Vim Tux (Install) 8.2.3290	79	Thursday, August 5, 2021	Approved
Vim Tux (Install) 8.2.3281	137	Wednesday, August 4, 2021	Approved
Vim Tux (Install) 8.2.3273	117	Monday, August 2, 2021	Approved
Vim Tux (Install) 8.2.3269	105	Monday, August 2, 2021	Approved
Vim Tux (Install) 8.2.3263	72	Sunday, August 1, 2021	Approved
Vim Tux (Install) 8.2.3253	107	Saturday, July 31, 2021	Approved
Vim Tux (Install) 8.2.3242	122	Thursday, July 29, 2021	Approved
Vim Tux (Install) 8.2.3204	157	Friday, July 23, 2021	Approved
Vim Tux (Install) 8.2.3187	174	Tuesday, July 20, 2021	Approved
Vim Tux (Install) 8.2.3171	188	Friday, July 16, 2021	Approved
Vim Tux (Install) 8.2.3158	207	Wednesday, July 14, 2021	Approved
Vim Tux (Install) 8.2.3154	169	Monday, July 12, 2021	Approved
Vim Tux (Install) 8.2.3131	156	Friday, July 9, 2021	Approved
Vim Tux (Install) 8.2.3120	137	Thursday, July 8, 2021	Approved
Vim Tux (Install) 8.2.3113	104	Wednesday, July 7, 2021	Approved
Vim Tux (Install) 8.2.3107	152	Monday, July 5, 2021	Approved
Vim Tux (Install) 8.2.3095	126	Sunday, July 4, 2021	Approved
Vim Tux (Install) 8.2.3080	172	Thursday, July 1, 2021	Approved
Vim Tux (Install) 8.2.3075	113	Wednesday, June 30, 2021	Approved
Vim Tux (Install) 8.2.3066	136	Monday, June 28, 2021	Approved
Vim Tux (Install) 8.2.3055	127	Sunday, June 27, 2021	Approved
Vim Tux (Install) 8.2.3043	146	Thursday, June 24, 2021	Exempted
Vim Tux (Install) 8.2.3033	186	Tuesday, June 22, 2021	Approved
Vim Tux (Install) 8.2.3017	139	Friday, June 18, 2021	Exempted
Vim Tux (Install) 8.2.2832	202	Wednesday, May 5, 2021	Exempted
Vim Tux (Install) 8.2.2799	263	Thursday, April 22, 2021	Approved
Vim Tux (Install) 8.2.2794	114	Wednesday, April 21, 2021	Approved
Vim Tux (Install) 8.2.2763	219	Thursday, April 15, 2021	Approved
Vim Tux (Install) 8.2.2738	198	Friday, April 9, 2021	Approved
Vim Tux (Install) 8.2.2730	140	Wednesday, April 7, 2021	Approved
Vim Tux (Install) 8.2.2679	176	Wednesday, March 31, 2021	Approved
Vim Tux (Install) 8.2.2650	110	Friday, March 26, 2021	Approved
Vim Tux (Install) 8.2.2648	269	Wednesday, March 24, 2021	Approved
Vim Tux (Install) 8.2.2417	293	Thursday, January 28, 2021	Approved
Vim Tux (Install) 8.2.2129	580	Saturday, December 12, 2020	Approved
Vim Tux (Install) 8.2.1981	485	Saturday, November 14, 2020	Approved
Vim Tux (Install) 8.2.1955	387	Friday, November 6, 2020	Approved
Vim Tux (Install) 8.2.1905	339	Monday, October 26, 2020	Approved
Vim Tux (Install) 8.2.1883	289	Thursday, October 22, 2020	Approved
Vim Tux (Install) 8.2.1858	308	Sunday, October 18, 2020	Approved
Vim Tux (Install) 8.2.1801	363	Monday, October 5, 2020	Approved
Vim Tux (Install) 8.2.1651	489	Thursday, September 10, 2020	Approved
Vim Tux (Install) 8.2.1139	819	Monday, July 6, 2020	Approved
Vim Tux (Install) 8.2.1058	505	Friday, June 26, 2020	Approved
Vim Tux (Install) 8.2.960	437	Friday, June 12, 2020	Approved
Vim Tux (Install) 8.2.950	264	Thursday, June 11, 2020	Approved
Vim Tux (Install) 8.2.916	283	Sunday, June 7, 2020	Approved
Vim Tux (Install) 8.2.882	414	Tuesday, June 2, 2020	Approved
Vim Tux (Install) 8.2.855	193	Sunday, May 31, 2020	Approved
Vim Tux (Install) 8.2.834	205	Friday, May 29, 2020	Approved
Vim Tux (Install) 8.2.829	316	Wednesday, May 27, 2020	Approved
Vim Tux (Install) 8.2.821	285	Tuesday, May 26, 2020	Approved
Vim Tux (Install) 8.2.806	264	Friday, May 22, 2020	Approved
Vim Tux (Install) 8.2.803	166	Thursday, May 21, 2020	Approved
Vim Tux (Install) 8.2.750	329	Thursday, May 14, 2020	Approved
Vim Tux (Install) 8.2.647	412	Monday, April 27, 2020	Approved
Vim Tux (Install) 8.2.640	249	Sunday, April 26, 2020	Approved
Vim Tux (Install) 8.2.625	283	Friday, April 24, 2020	Approved
Vim Tux (Install) 8.2.612	272	Tuesday, April 21, 2020	Approved
Vim Tux (Install) 8.2.592	215	Saturday, April 18, 2020	Approved
Vim Tux (Install) 8.2.585	227	Friday, April 17, 2020	Approved
Vim Tux (Install) 8.2.577	238	Wednesday, April 15, 2020	Approved
Vim Tux (Install) 8.2.0357	668	Friday, March 6, 2020	Approved
Vim Tux (Install) 8.2.0324	359	Friday, February 28, 2020	Approved
Vim Tux (Install) 8.2.0313	289	Monday, February 24, 2020	Approved
Vim Tux (Install) 8.2.0294	233	Saturday, February 22, 2020	Approved
Vim Tux (Install) 8.2.0285	206	Friday, February 21, 2020	Approved
Vim Tux (Install) 8.2.0273	275	Tuesday, February 18, 2020	Approved
Vim Tux (Install) 8.2.0231	363	Sunday, February 9, 2020	Approved
Vim Tux (Install) 8.2.0184	360	Friday, January 31, 2020	Approved
Vim Tux (Install) 8.2.0164	267	Wednesday, January 29, 2020	Approved
Vim Tux (Install) 8.2.0140	302	Wednesday, January 22, 2020	Approved
Vim Tux (Install) 8.2.0129	326	Sunday, January 19, 2020	Approved
Vim Tux (Install) 8.2.0114	450	Tuesday, January 14, 2020	Approved
Vim Tux (Install) 8.2.0109	289	Friday, January 10, 2020	Approved
Vim Tux (Install) 8.2.0092	362	Tuesday, January 7, 2020	Approved
Vim Tux (Install) 8.2.0080	498	Friday, January 3, 2020	Approved
Vim Tux (Install) 8.1.2333	827	Friday, November 22, 2019	Approved
Vim Tux (Install) 8.1.2323	413	Thursday, November 21, 2019	Approved
Vim Tux (Install) 8.1.2311	494	Sunday, November 17, 2019	Approved
Vim Tux (Install) 8.1.2300	405	Thursday, November 14, 2019	Approved
Vim Tux (Install) 8.1.2237	614	Friday, November 1, 2019	Approved
Vim Tux (Install) 8.1.2204	628	Thursday, October 24, 2019	Approved
Vim Tux (Install) 8.1.2200	405	Wednesday, October 23, 2019	Approved
Vim Tux (Install) 8.1.2148	722	Monday, October 14, 2019	Approved
Vim Tux (Install) 8.1.2133	468	Friday, October 11, 2019	Approved
Vim Tux (Install) 8.1.2117	563	Sunday, October 6, 2019	Approved
Vim Tux (Install) 8.1.2108	435	Thursday, October 3, 2019	Approved
Vim Tux (Install) 8.1.2103	436	Tuesday, October 1, 2019	Approved
Vim Tux (Install) 8.1.2079	503	Friday, September 27, 2019	Approved
Vim Tux (Install) 8.1.2071	475	Wednesday, September 25, 2019	Approved
Vim Tux (Install) 8.1.2052	587	Thursday, September 19, 2019	Approved
Vim Tux (Install) 8.1.2019	648	Tuesday, September 10, 2019	Approved
Vim Tux (Install) 8.1.2004	466	Sunday, September 8, 2019	Approved
Vim Tux (Install) 8.1.1995	325	Saturday, September 7, 2019	Approved
Vim Tux (Install) 8.1.1986	433	Thursday, September 5, 2019	Approved
Vim Tux (Install) 8.1.1961	459	Monday, September 2, 2019	Approved
Vim Tux (Install) 8.1.1927	586	Monday, August 26, 2019	Approved
Vim Tux (Install) 8.1.1915	317	Saturday, August 24, 2019	Approved
Vim Tux (Install) 8.1.1906	367	Thursday, August 22, 2019	Approved
Vim Tux (Install) 8.1.1890	409	Tuesday, August 20, 2019	Approved
Vim Tux (Install) 8.1.1836	529	Sunday, August 11, 2019	Approved
Vim Tux (Install) 8.1.1744	708	Thursday, July 25, 2019	Approved
Vim Tux (Install) 8.1.1729	401	Tuesday, July 23, 2019	Approved
Vim Tux (Install) 8.1.1713	419	Friday, July 19, 2019	Approved
Vim Tux (Install) 8.1.1695	431	Tuesday, July 16, 2019	Approved
Vim Tux (Install) 8.1.1669	440	Saturday, July 13, 2019	Approved
Vim Tux (Install) 8.1.1655	525	Tuesday, July 9, 2019	Approved
Vim Tux (Install) 8.1.1631	426	Friday, July 5, 2019	Approved
Vim Tux (Install) 8.1.1601	541	Thursday, June 27, 2019	Approved
Vim Tux (Install) 8.1.1587	384	Tuesday, June 25, 2019	Approved
Vim Tux (Install) 8.1.1573	425	Thursday, June 20, 2019	Approved
Vim Tux (Install) 8.1.1566	483	Tuesday, June 18, 2019	Approved
Vim Tux (Install) 8.1.1557	300	Monday, June 17, 2019	Approved
Vim Tux (Install) 8.1.1536	313	Sunday, June 16, 2019	Approved
Vim Tux (Install) 8.1.1523	302	Friday, June 14, 2019	Approved
Vim Tux (Install) 8.1.1515	355	Tuesday, June 11, 2019	Approved
Vim Tux (Install) 8.1.1511	421	Monday, June 10, 2019	Approved
Vim Tux (Install) 8.1.1455	504	Monday, June 3, 2019	Approved
Vim Tux (Install) 8.1.1432	337	Friday, May 31, 2019	Approved
Vim Tux (Install) 8.1.1413	371	Tuesday, May 28, 2019	Approved
Vim Tux (Install) 8.1.1373	467	Friday, May 24, 2019	Approved
Vim Tux (Install) 8.1.1364	317	Thursday, May 23, 2019	Approved
Vim Tux (Install) 8.1.1353	474	Monday, May 20, 2019	Approved
Vim Tux (Install) 8.1.1333	446	Thursday, May 16, 2019	Approved
Vim Tux (Install) 8.1.1328	412	Monday, May 13, 2019	Approved
Vim Tux (Install) 8.1.1312	294	Saturday, May 11, 2019	Approved
Vim Tux (Install) 8.1.1298	367	Thursday, May 9, 2019	Approved
Vim Tux (Install) 8.1.1286	382	Tuesday, May 7, 2019	Approved
Vim Tux (Install) 8.1.1229	529	Monday, April 29, 2019	Approved
Vim Tux (Install) 8.1.1183	405	Thursday, April 18, 2019	Approved
Vim Tux (Install) 8.1.1173	405	Monday, April 15, 2019	Approved
Vim Tux (Install) 8.1.1165	294	Sunday, April 14, 2019	Approved
Vim Tux (Install) 8.1.1140	471	Tuesday, April 9, 2019	Approved
Vim Tux (Install) 8.1.1136	361	Monday, April 8, 2019	Approved
Vim Tux (Install) 8.1.1124	297	Sunday, April 7, 2019	Approved
Vim Tux (Install) 8.1.1116	339	Thursday, April 4, 2019	Approved
Vim Tux (Install) 8.1.1103	327	Thursday, April 4, 2019	Approved
Vim Tux (Install) 8.1.1097	286	Monday, April 1, 2019	Approved
Vim Tux (Install) 8.1.1073	443	Saturday, March 30, 2019	Approved
Vim Tux (Install) 8.1.1057	396	Thursday, March 28, 2019	Approved
Vim Tux (Install) 8.1.1045	185	Sunday, March 24, 2019	Approved
Vim Tux (Install) 8.1.1032	159	Friday, March 22, 2019	Approved
Vim Tux (Install) 8.1.1027	510	Thursday, March 21, 2019	Approved
Vim Tux (Install) 8.1.1017	333	Tuesday, March 19, 2019	Approved
Vim Tux (Install) 8.1.1004	592	Monday, March 11, 2019	Approved
Vim Tux (Install) 8.1.998	399	Friday, March 8, 2019	Approved
Vim Tux (Install) 8.1.990	527	Sunday, March 3, 2019	Approved
Vim Tux (Install) 8.1.984	421	Thursday, February 28, 2019	Approved
Vim Tux (Install) 8.1.978	436	Saturday, February 23, 2019	Approved
Vim Tux (Install) 8.1.966	342	Friday, February 22, 2019	Approved
Vim Tux (Install) 8.1.947	438	Tuesday, February 19, 2019	Approved
Vim Tux (Install) 8.1.934	311	Sunday, February 17, 2019	Approved
Vim Tux (Install) 8.1.926	311	Saturday, February 16, 2019	Approved
Vim Tux (Install) 8.1.909	330	Thursday, February 14, 2019	Approved
Vim Tux (Install) 8.1.895	361	Tuesday, February 12, 2019	Approved
Vim Tux (Install) 8.1.0885	339	Sunday, February 10, 2019	Approved
Vim Tux (Install) 8.1.0877	195	Thursday, February 7, 2019	Approved
Vim Tux (Install) 8.1.0871	421	Monday, February 4, 2019	Approved
Vim Tux (Install) 8.1.0868	281	Sunday, February 3, 2019	Approved
Vim Tux (Install) 8.1.0865	292	Saturday, February 2, 2019	Approved
Vim Tux (Install) 8.1.0842	293	Thursday, January 31, 2019	Approved
Vim Tux (Install) 8.1.0837	378	Monday, January 28, 2019	Approved
Vim Tux (Install) 8.1.0814	350	Friday, January 25, 2019	Approved
Vim Tux (Install) 8.1.0796	298	Thursday, January 24, 2019	Approved
Vim Tux (Install) 8.1.0788	334	Tuesday, January 22, 2019	Approved
Vim Tux (Install) 8.1.0712	471	Thursday, January 10, 2019	Approved
Vim Tux (Install) 8.1.0700	360	Tuesday, January 8, 2019	Approved
Vim Tux (Install) 8.1.0690	425	Saturday, January 5, 2019	Approved
Vim Tux (Install) 8.1.0681	296	Thursday, January 3, 2019	Approved
Vim Tux (Install) 8.1.0674	305	Wednesday, January 2, 2019	Approved
Vim Tux (Install) 8.1.0647	355	Friday, December 28, 2018	Approved
Vim Tux (Install) 8.1.0635	319	Wednesday, December 26, 2018	Approved
Vim Tux (Install) 8.1.0630	256	Tuesday, December 25, 2018	Approved
Vim Tux (Install) 8.1.0629	261	Monday, December 24, 2018	Approved
Vim Tux (Install) 8.1.0622	230	Sunday, December 23, 2018	Approved
Vim Tux (Install) 8.1.0617	338	Saturday, December 22, 2018	Approved
Vim Tux (Install) 8.1.0594	480	Sunday, December 16, 2018	Approved
Vim Tux (Install) 8.1.0577	345	Thursday, December 13, 2018	Approved
Vim Tux (Install) 8.1.0551	593	Friday, November 30, 2018	Approved
Vim Tux (Install) 8.1.0547	447	Monday, November 26, 2018	Approved
Vim Tux (Install) 8.1.0536	422	Tuesday, November 20, 2018	Approved
Vim Tux (Install) 8.1.0524	454	Tuesday, November 13, 2018	Approved
Vim Tux (Install) 8.1.0513	358	Thursday, November 8, 2018	Approved
Vim Tux (Install) 8.1.0509	383	Sunday, November 4, 2018	Approved
Vim Tux (Install) 8.1.0498	450	Sunday, October 28, 2018	Approved
Vim Tux (Install) 8.1.0489	394	Monday, October 22, 2018	Approved
Vim Tux (Install) 8.1.0474	478	Monday, October 15, 2018	Approved
Vim Tux (Install) 8.1.0470	375	Friday, October 12, 2018	Approved
Vim Tux (Install) 8.1.0451	451	Friday, October 5, 2018	Approved
Vim Tux (Install) 8.1.0442	429	Monday, October 1, 2018	Approved
Vim Tux (Install) 8.1.0436	405	Thursday, September 27, 2018	Approved
Vim Tux (Install) 8.1.0425	453	Saturday, September 22, 2018	Approved
Vim Tux (Install) 8.1.0408	308	Thursday, September 20, 2018	Approved
Vim Tux (Install) 8.1.0401	299	Tuesday, September 18, 2018	Approved
Vim Tux (Install) 8.1.0385	444	Friday, September 14, 2018	Approved
Vim Tux (Install) 8.1.0371	320	Thursday, September 13, 2018	Approved
Vim Tux (Install) 8.1.0362	365	Tuesday, September 11, 2018	Approved
Vim Tux (Install) 8.1.0354	330	Sunday, September 9, 2018	Approved
Vim Tux (Install) 8.1.0347	358	Thursday, September 6, 2018	Approved
Vim Tux (Install) 8.1.0342	343	Sunday, September 2, 2018	Approved
Vim Tux (Install) 8.1.0332	371	Thursday, August 30, 2018	Approved
Vim Tux (Install) 8.1.0327	384	Sunday, August 26, 2018	Approved
Vim Tux (Install) 8.1.0318	308	Thursday, August 23, 2018	Approved
Vim Tux (Install) 8.1.0301	222	Tuesday, August 21, 2018	Approved
Vim Tux (Install) 8.1.0297	354	Monday, August 20, 2018	Approved
Vim Tux (Install) 8.1.0288	365	Thursday, August 16, 2018	Approved
Vim Tux (Install) 8.1.0278	365	Monday, August 13, 2018	Approved
Vim Tux (Install) 8.1.0271	286	Sunday, August 12, 2018	Approved
Vim Tux (Install) 8.1.0259	368	Friday, August 10, 2018	Approved
Vim Tux (Install) 8.1.0239	423	Sunday, August 5, 2018	Approved
Vim Tux (Install) 8.1.0229	387	Tuesday, July 31, 2018	Approved
Vim Tux (Install) 8.1.0221	320	Sunday, July 29, 2018	Approved
Vim Tux (Install) 8.1.0210	348	Thursday, July 26, 2018	Approved
Vim Tux (Install) 8.1.0207	320	Tuesday, July 24, 2018	Approved
Vim Tux (Install) 8.1.0203	365	Monday, July 23, 2018	Approved
Vim Tux (Install) 8.1.0199	357	Saturday, July 21, 2018	Approved
Vim Tux (Install) 8.1.0196	310	Friday, July 20, 2018	Approved
Vim Tux (Install) 8.1.0191	360	Tuesday, July 17, 2018	Approved
Vim Tux (Install) 8.1.0186	330	Sunday, July 15, 2018	Approved
Vim Tux (Install) 8.1.0173	431	Tuesday, July 10, 2018	Approved
Vim Tux (Install) 8.1.0153	421	Friday, July 6, 2018	Approved
Vim Tux (Install) 8.1.0138	362	Tuesday, July 3, 2018	Approved
Vim Tux (Install) 8.1.0133	491	Sunday, July 1, 2018	Approved
Vim Tux (Install) 8.1.0126	371	Friday, June 29, 2018	Approved
Vim Tux (Install) 8.1.0105	391	Sunday, June 24, 2018	Approved
Vim Tux (Install) 8.1.0054	589	Thursday, June 14, 2018	Approved
Vim Tux (Install) 8.1.0034	639	Tuesday, June 5, 2018	Approved
Vim Tux (Install) 8.1.0022	499	Friday, May 25, 2018	Approved
Vim Tux (Install) 8.1.0013	428	Tuesday, May 22, 2018	Approved
Vim Tux (Install) 8.1.0009	326	Monday, May 21, 2018	Approved
Vim Tux (Install) 8.1.0004	283	Sunday, May 20, 2018	Approved
Vim Tux (Install) 8.1.0000	343	Saturday, May 19, 2018	Approved
Vim Tux (Install) 8.0.1848	344	Thursday, May 17, 2018	Approved
Vim Tux (Install) 8.0.1831	402	Monday, May 14, 2018	Approved
Vim Tux (Install) 8.0.1820	347	Sunday, May 13, 2018	Approved
Vim Tux (Install) 8.0.1806	414	Thursday, May 10, 2018	Approved
Vim Tux (Install) 8.0.1799	410	Monday, May 7, 2018	Approved
Vim Tux (Install) 8.0.1794	289	Sunday, May 6, 2018	Approved
Vim Tux (Install) 8.0.1790	332	Friday, May 4, 2018	Approved
Vim Tux (Install) 8.0.1788	380	Thursday, May 3, 2018	Approved
Vim Tux (Install) 8.0.1774	422	Monday, April 30, 2018	Approved
Vim Tux (Install) 8.0.1765	445	Thursday, April 26, 2018	Approved
Vim Tux (Install) 8.0.1748	374	Sunday, April 22, 2018	Approved
Vim Tux (Install) 8.0.1736	334	Friday, April 20, 2018	Approved
Vim Tux (Install) 8.0.1727	355	Wednesday, April 18, 2018	Approved
Vim Tux (Install) 8.0.1705	402	Saturday, April 14, 2018	Approved
Vim Tux (Install) 8.0.1679	457	Monday, April 9, 2018	Approved
Vim Tux (Install) 8.0.1664	360	Saturday, April 7, 2018	Approved
Vim Tux (Install) 8.0.1655	435	Saturday, March 31, 2018	Approved
Vim Tux (Install) 8.0.1638	558	Sunday, March 25, 2018	Approved
Vim Tux (Install) 8.0.1626	449	Thursday, March 22, 2018	Approved
Vim Tux (Install) 8.0.1612	453	Saturday, March 17, 2018	Approved
Vim Tux (Install) 8.0.1601	473	Tuesday, March 13, 2018	Approved
Vim Tux (Install) 8.0.1591	432	Friday, March 9, 2018	Approved
Vim Tux (Install) 8.0.1563	457	Sunday, March 4, 2018	Approved
Vim Tux (Install) 8.0.1553	328	Friday, March 2, 2018	Approved
Vim Tux (Install) 8.0.1532	524	Sunday, February 25, 2018	Approved
Vim Tux (Install) 8.0.1504	632	Thursday, February 15, 2018	Approved
Vim Tux (Install) 8.0.1473	490	Thursday, February 8, 2018	Approved
Vim Tux (Install) 8.0.1451	471	Saturday, February 3, 2018	Approved
Vim Tux (Install) 8.0.1438	432	Tuesday, January 30, 2018	Approved
Vim Tux (Install) 8.0.1431	468	Saturday, January 27, 2018	Approved
Vim Tux (Install) 8.0.1428	676	Thursday, January 4, 2018	Approved
Vim Tux (Install) 8.0.1422	454	Saturday, December 30, 2017	Approved
Vim Tux (Install) 8.0.1390	556	Sunday, December 17, 2017	Approved
Vim Tux (Install) 8.0.1379	411	Thursday, December 14, 2017	Approved
Vim Tux (Install) 8.0.1376	472	Thursday, December 7, 2017	Approved
Vim Tux (Install) 8.0.1358	542	Friday, December 1, 2017	Approved
Vim Tux (Install) 8.0.1330	543	Thursday, November 23, 2017	Approved
Vim Tux (Install) 8.0.1311	450	Monday, November 20, 2017	Approved
Vim Tux (Install) 8.0.1305	437	Saturday, November 18, 2017	Approved
Vim Tux (Install) 8.0.1272	561	Thursday, November 9, 2017	Approved
Vim Tux (Install) 8.0.1257	482	Sunday, November 5, 2017	Approved
Vim Tux (Install) 8.0.1203	621	Wednesday, October 18, 2017	Approved
Vim Tux (Install) 8.0.1157	658	Friday, September 29, 2017	Approved
Vim Tux (Install) 8.0.1088	662	Monday, September 11, 2017	Approved
Vim Tux (Install) 8.0.1010	586	Tuesday, August 29, 2017	Approved
Vim Tux (Install) 8.0.0737	745	Thursday, July 20, 2017	Approved
Vim Tux (Install) 8.0.0642	715	Sunday, June 18, 2017	Approved
Vim Tux (Install) 8.0.0584	897	Wednesday, April 26, 2017	Approved
Vim Tux (Install) 8.0.0575	529	Friday, April 21, 2017	Approved
Vim Tux (Install) 8.0.0430	897	Thursday, March 9, 2017	Approved
Vim Tux (Install) 8.0.0320	778	Friday, February 10, 2017	Approved
Vim Tux (Install) 8.0.0206	738	Friday, January 20, 2017	Approved
Vim Tux (Install) 8.0.0194	444	Tuesday, January 17, 2017	Approved
Vim Tux (Install) 8.0.0123	832	Friday, December 9, 2016	Approved
Vim Tux (Install) 8.0.0117	486	Friday, December 2, 2016	Approved
Vim Tux (Install) 8.0.0066	685	Thursday, November 10, 2016	Approved
Vim Tux (Install) 8.0.0051	619	Friday, October 28, 2016	Approved
Vim Tux (Install) 8.0.0045	503	Friday, October 21, 2016	Approved
Vim Tux (Install) 8.0.0017	571	Wednesday, September 28, 2016	Approved
Vim Tux (Install) 8.0.005	639	Friday, September 16, 2016	Approved
Vim Tux (Install) 7.4.2222	714	Thursday, August 18, 2016	Approved
Vim Tux (Install) 7.4.2180	347	Tuesday, August 9, 2016	Approved
Vim Tux (Install) 7.4.2153	371	Friday, August 5, 2016	Approved
Vim Tux (Install) 7.4.2089	584	Friday, July 22, 2016	Approved
Vim Tux (Install) 7.4.2034	326	Friday, July 15, 2016	Approved
Vim Tux (Install) 7.4.1998	348	Friday, July 8, 2016	Approved
Vim Tux (Install) 7.4.1987	389	Sunday, July 3, 2016	Approved
Vim Tux (Install) 7.4.1949	361	Thursday, June 23, 2016	Approved
Vim Tux (Install) 7.4.1913	387	Friday, June 10, 2016	Approved
Vim Tux (Install) 7.4.1905	431	Thursday, June 9, 2016	Approved
Vim Tux (Install) 7.4.1901	389	Tuesday, June 7, 2016	Approved
Vim Tux (Install) 7.4.1862	363	Thursday, June 2, 2016	Approved
Vim Tux (Install) 7.4.1856	351	Monday, May 30, 2016	Approved
Vim Tux (Install) 7.4.1848	357	Friday, May 27, 2016	Approved
Vim Tux (Install) 7.4.1842	345	Thursday, May 26, 2016	Approved
Vim Tux (Install) 7.4.1832	349	Thursday, May 19, 2016	Approved
Vim Tux (Install) 7.4.1829	340	Thursday, May 12, 2016	Approved
Vim Tux (Install) 7.4.1824	376	Monday, May 9, 2016	Approved

Release Notes

http://ftp.vim.org/pub/vim/patches/9.0/README

Dependencies

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

140,108

34

10 Nov 2022

Vim Tux (Install)

Vim Tux (Install)

Some Checks Have Failed or Are Not Yet Complete

LinkSatonaka (maintainer) on 10 Nov 2022 00:08:09 +00:00:

chocolatey-ops (reviewer) on 10 Nov 2022 00:41:37 +00:00:

Guidelines

Suggestions

Notes

chocolatey-ops (reviewer) on 10 Nov 2022 02:19:57 +00:00:

chocolatey-ops (reviewer) on 30 Nov 2022 00:44:55 +00:00:

chocolatey-ops (reviewer) on 15 Dec 2022 00:47:30 +00:00:

Package Parameters

Ground Rules: