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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

- name: Install and Configure Chocolatey
  hosts: all

## 2. TOP LEVEL VARIABLES ##
  vars:

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

chocolatey_feature 'useBackgroundService' do
  action :enable
end

chocolatey_feature 'useBackgroundServiceWithNonAdministratorsOnly' do
  action :enable
end

chocolatey_feature 'allowBackgroundServiceUninstallsFromUserInstallsOnly' do
  action :enable
end

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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


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

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

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

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

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


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


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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Need Help? View our docs or file an issue.

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

Current Version	New Version

Downloads:

68,163

Downloads of v 8.2.3356:

54

Last Update:

18 Aug 2021

Package Maintainer(s):

Pauby

Software Author(s):

Build: TuxProject.de
Developer: vim team

Tags:

vim-tux vim editor tux

Vim Tux (Portable)

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

8.2.3356 | Updated: 18 Aug 2021

Downloads:

68,163

Downloads of v 8.2.3356:

Maintainer(s):

Pauby

Software Author(s):

Build: TuxProject.de
Developer: vim team

Tags:

vim-tux vim editor tux

Vim Tux (Portable) 8.2.3356

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

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Hide Checks

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Resulted in Flagged as a Note:

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

Details

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

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

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

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

NOTE

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

1. Enter Your Internal Repository Url

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

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

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

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

Option 2: Internalized Package (Reliable, Scalable)

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

Package Internalizer (C4B)

Run: (additional options)

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

For package and dependencies run:

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

Automate package internalization

3. Copy Your Script

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

See options you can pass to upgrade.

See best practices for scripting.

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

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


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

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

Exit $exitCode


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

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


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

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


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

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


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

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

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

NOTE

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

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

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

Package Approved

This package was approved as a trusted package on 18 Aug 2021.

Description

Please visit the official site at https://tuxproject.de/projects/vim/ for more information.

Used libraries: Perl 5.24.0, Python 2.7.12, Python 3.5.2, Racket 6.6, Ruby 2.3.0, Lua 5.3.3, Tcl 8.6.4, libXpm.
Build provided by TuxProject.de - consider donating to help support their server costs.

Files

tools\vim82\xxd.exe.ignore

tools\vim82\winpty-agent.exe.ignore

tools\vim82\vimrun.exe.ignore

tools\vim82\vimdiff.bat

@echo off
rem -- Run Vim --
rem # uninstall key: vim82 #

setlocal
set VIM_EXE_DIR=C:\Program Files\Vim\vim82
if exist "%VIM%\vim82\vim.exe" set VIM_EXE_DIR=%VIM%\vim82
if exist "%VIMRUNTIME%\vim.exe" set VIM_EXE_DIR=%VIMRUNTIME%

if exist "%VIM_EXE_DIR%\vim.exe" goto havevim
echo "%VIM_EXE_DIR%\vim.exe" not found
goto eof

:havevim
rem collect the arguments in VIMARGS for Win95
set VIMARGS=
:loopstart
if .%1==. goto loopend
set VIMARGS=%VIMARGS% %1
shift
goto loopstart
:loopend

if .%OS%==.Windows_NT goto ntaction

"%VIM_EXE_DIR%\vim.exe" -d %VIMARGS%
goto eof

:ntaction
rem for WinNT we can use %*
"%VIM_EXE_DIR%\vim.exe" -d %*
goto eof


:eof
set VIMARGS=

tools\vim82\vim.exe.ignore

tools\vim82\vim.bat

@echo off
rem -- Run Vim --
rem # uninstall key: vim82 #

setlocal
set VIM_EXE_DIR=C:\Program Files\Vim\vim82
if exist "%VIM%\vim82\vim.exe" set VIM_EXE_DIR=%VIM%\vim82
if exist "%VIMRUNTIME%\vim.exe" set VIM_EXE_DIR=%VIMRUNTIME%

if exist "%VIM_EXE_DIR%\vim.exe" goto havevim
echo "%VIM_EXE_DIR%\vim.exe" not found
goto eof

:havevim
rem collect the arguments in VIMARGS for Win95
set VIMARGS=
:loopstart
if .%1==. goto loopend
set VIMARGS=%VIMARGS% %1
shift
goto loopstart
:loopend

if .%OS%==.Windows_NT goto ntaction

"%VIM_EXE_DIR%\vim.exe"  %VIMARGS%
goto eof

:ntaction
rem for WinNT we can use %*
"%VIM_EXE_DIR%\vim.exe"  %*
goto eof


:eof
set VIMARGS=

tools\vim82\view.bat

@echo off
rem -- Run Vim --
rem # uninstall key: vim82 #

setlocal
set VIM_EXE_DIR=C:\Program Files\Vim\vim82
if exist "%VIM%\vim82\vim.exe" set VIM_EXE_DIR=%VIM%\vim82
if exist "%VIMRUNTIME%\vim.exe" set VIM_EXE_DIR=%VIMRUNTIME%

if exist "%VIM_EXE_DIR%\vim.exe" goto havevim
echo "%VIM_EXE_DIR%\vim.exe" not found
goto eof

:havevim
rem collect the arguments in VIMARGS for Win95
set VIMARGS=
:loopstart
if .%1==. goto loopend
set VIMARGS=%VIMARGS% %1
shift
goto loopstart
:loopend

if .%OS%==.Windows_NT goto ntaction

"%VIM_EXE_DIR%\vim.exe" -R %VIMARGS%
goto eof

:ntaction
rem for WinNT we can use %*
"%VIM_EXE_DIR%\vim.exe" -R %*
goto eof


:eof
set VIMARGS=

tools\vim82\uninstal.exe.ignore

tools\vim82\tee.exe.ignore

tools\vim82\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\vim82\patch.exe.ignore

tools\vim82\install.exe.ignore

tools\vim82\gvim_noOLE.exe.ignore

tools\vim82\gvimdiff.bat

@echo off
rem -- Run Vim --
rem # uninstall key: vim82 #

setlocal
set VIM_EXE_DIR=C:\Program Files\Vim\vim82
if exist "%VIM%\vim82\gvim.exe" set VIM_EXE_DIR=%VIM%\vim82
if exist "%VIMRUNTIME%\gvim.exe" set VIM_EXE_DIR=%VIMRUNTIME%

if exist "%VIM_EXE_DIR%\gvim.exe" goto havevim
echo "%VIM_EXE_DIR%\gvim.exe" not found
goto eof

:havevim
rem collect the arguments in VIMARGS for Win95
set VIMARGS=
set VIMNOFORK=
:loopstart
if .%1==. goto loopend
if NOT .%1==.--nofork goto noforklongarg
set VIMNOFORK=1
:noforklongarg
if NOT .%1==.-f goto noforkarg
set VIMNOFORK=1
:noforkarg
set VIMARGS=%VIMARGS% %1
shift
goto loopstart
:loopend

if .%OS%==.Windows_NT goto ntaction

if .%VIMNOFORK%==.1 goto nofork
start "%VIM_EXE_DIR%\gvim.exe" -d %VIMARGS%
goto eof

:nofork
start /w "%VIM_EXE_DIR%\gvim.exe" -d %VIMARGS%
goto eof

:ntaction
rem for WinNT we can use %*
if .%VIMNOFORK%==.1 goto noforknt
start "dummy" /b "%VIM_EXE_DIR%\gvim.exe" -d %*
goto eof

:noforknt
start "dummy" /b /wait "%VIM_EXE_DIR%\gvim.exe" -d %*

:eof
set VIMARGS=
set VIMNOFORK=

tools\vim82\gvim.exe.ignore

tools\vim82\gvim.bat

@echo off
rem -- Run Vim --
rem # uninstall key: vim82 #

setlocal
set VIM_EXE_DIR=C:\Program Files\Vim\vim82
if exist "%VIM%\vim82\gvim.exe" set VIM_EXE_DIR=%VIM%\vim82
if exist "%VIMRUNTIME%\gvim.exe" set VIM_EXE_DIR=%VIMRUNTIME%

if exist "%VIM_EXE_DIR%\gvim.exe" goto havevim
echo "%VIM_EXE_DIR%\gvim.exe" not found
goto eof

:havevim
rem collect the arguments in VIMARGS for Win95
set VIMARGS=
set VIMNOFORK=
:loopstart
if .%1==. goto loopend
if NOT .%1==.--nofork goto noforklongarg
set VIMNOFORK=1
:noforklongarg
if NOT .%1==.-f goto noforkarg
set VIMNOFORK=1
:noforkarg
set VIMARGS=%VIMARGS% %1
shift
goto loopstart
:loopend

if .%OS%==.Windows_NT goto ntaction

if .%VIMNOFORK%==.1 goto nofork
start "%VIM_EXE_DIR%\gvim.exe"  %VIMARGS%
goto eof

:nofork
start /w "%VIM_EXE_DIR%\gvim.exe"  %VIMARGS%
goto eof

:ntaction
rem for WinNT we can use %*
if .%VIMNOFORK%==.1 goto noforknt
start "dummy" /b "%VIM_EXE_DIR%\gvim.exe"  %*
goto eof

:noforknt
start "dummy" /b /wait "%VIM_EXE_DIR%\gvim.exe"  %*

:eof
set VIMARGS=
set VIMNOFORK=

tools\vim82\gview.bat

@echo off
rem -- Run Vim --
rem # uninstall key: vim82 #

setlocal
set VIM_EXE_DIR=C:\Program Files\Vim\vim82
if exist "%VIM%\vim82\gvim.exe" set VIM_EXE_DIR=%VIM%\vim82
if exist "%VIMRUNTIME%\gvim.exe" set VIM_EXE_DIR=%VIMRUNTIME%

if exist "%VIM_EXE_DIR%\gvim.exe" goto havevim
echo "%VIM_EXE_DIR%\gvim.exe" not found
goto eof

:havevim
rem collect the arguments in VIMARGS for Win95
set VIMARGS=
set VIMNOFORK=
:loopstart
if .%1==. goto loopend
if NOT .%1==.--nofork goto noforklongarg
set VIMNOFORK=1
:noforklongarg
if NOT .%1==.-f goto noforkarg
set VIMNOFORK=1
:noforkarg
set VIMARGS=%VIMARGS% %1
shift
goto loopstart
:loopend

if .%OS%==.Windows_NT goto ntaction

if .%VIMNOFORK%==.1 goto nofork
start "%VIM_EXE_DIR%\gvim.exe" -R %VIMARGS%
goto eof

:nofork
start /w "%VIM_EXE_DIR%\gvim.exe" -R %VIMARGS%
goto eof

:ntaction
rem for WinNT we can use %*
if .%VIMNOFORK%==.1 goto noforknt
start "dummy" /b "%VIM_EXE_DIR%\gvim.exe" -R %*
goto eof

:noforknt
start "dummy" /b /wait "%VIM_EXE_DIR%\gvim.exe" -R %*

:eof
set VIMARGS=
set VIMNOFORK=

tools\vim82\evim.bat

@echo off
rem -- Run Vim --
rem # uninstall key: vim82 #

setlocal
set VIM_EXE_DIR=C:\Program Files\Vim\vim82
if exist "%VIM%\vim82\gvim.exe" set VIM_EXE_DIR=%VIM%\vim82
if exist "%VIMRUNTIME%\gvim.exe" set VIM_EXE_DIR=%VIMRUNTIME%

if exist "%VIM_EXE_DIR%\gvim.exe" goto havevim
echo "%VIM_EXE_DIR%\gvim.exe" not found
goto eof

:havevim
rem collect the arguments in VIMARGS for Win95
set VIMARGS=
set VIMNOFORK=
:loopstart
if .%1==. goto loopend
if NOT .%1==.--nofork goto noforklongarg
set VIMNOFORK=1
:noforklongarg
if NOT .%1==.-f goto noforkarg
set VIMNOFORK=1
:noforkarg
set VIMARGS=%VIMARGS% %1
shift
goto loopstart
:loopend

if .%OS%==.Windows_NT goto ntaction

if .%VIMNOFORK%==.1 goto nofork
start "%VIM_EXE_DIR%\gvim.exe" -y %VIMARGS%
goto eof

:nofork
start /w "%VIM_EXE_DIR%\gvim.exe" -y %VIMARGS%
goto eof

:ntaction
rem for WinNT we can use %*
if .%VIMNOFORK%==.1 goto noforknt
start "dummy" /b "%VIM_EXE_DIR%\gvim.exe" -y %*
goto eof

:noforknt
start "dummy" /b /wait "%VIM_EXE_DIR%\gvim.exe" -y %*

:eof
set VIMARGS=
set VIMNOFORK=

tools\vim82\diff.exe.ignore

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: A44E306755545927B44672353997C788313AE4CD35AEF42040F79F77DACBC310
  checksum64: 554181480D54CD497F800BE4949B1C5F1DF06FB170F63E1B6FCB55916CEA6136

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

tools\LICENSE.txt

*uganda.txt*    For Vim version 8.1.  Last change: 2018 May 17


		  VIM REFERENCE MANUAL    by Bram Moolenaar


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

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

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

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

=== begin of license ===

VIM LICENSE

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

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

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

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

=== end of license ===

Note:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Sending money:						*iccf-donations*

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


USA:		The methods mentioned below can be used.
		Sending a check to the Nehemiah Group Outreach Society (NGOS)
		is no longer possible, unfortunately. We are looking for
		another way to get you an IRS tax receipt. 
		For sponsoring a child contact KCF in Canada (see below). US
		checks can be sent to them to lower banking costs.

Canada:		Contact Kibaale Children's Fund (KCF) in Surrey, Canada.  They
		take care of the Canadian sponsors for the children in
		Kibaale.  KCF forwards 100% of the money to the project in
		Uganda.  You can send them a one time donation directly.
		Please send me a note so that I know what has been donated
		because of Vim.  Ask KCF for information about sponsorship.
			Kibaale Children's Fund c/o Pacific Academy
			10238-168 Street
			Surrey, B.C. V4N 1Z4
			Canada
			Phone: 604-581-5353
		If you make a donation to Kibaale Children's Fund (KCF) you
		will receive a tax receipt which can be submitted with your
		tax return.

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

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

World:		Use a postal money order.  That should be possible from any
		country, mostly from the post office.  Use this name (which is
		in my passport): "Abraham Moolenaar".  Use Euro for the
		currency if possible.

Europe:		Use a bank transfer if possible.  Your bank should have a form
		that you can use for this.  See "Others" below for the swift
		code and IBAN number.
		Any other method should work.  Ask for information about
		sponsorship.

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

Others:		Transfer to one of these accounts if possible:
		    Postbank, account 4548774
				Swift code: INGB NL 2A
				IBAN: NL95 INGB 0004 5487 74
			under the name "stichting ICCF Holland", Lisse
		    If that doesn't work:
		    Rabobank Lisse, account 3765.05.117
				Swift code: RABO NL 2U
			under the name "Bram Moolenaar", Lisse
		Otherwise, send a check in euro or US dollars to the address
		below.  Minimal amount: $70 (my bank does not accept smaller
		amounts for foreign check, sorry)

Address to send checks to:
			Bram Moolenaar
			Finsterruetihof 1
			8134 Adliswil
			Switzerland

This address is expected to be valid for a long time.

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

tools\complete-x86_x32.exe

md5: A168B500DEB0FB0B3C0357084C250D07 | sha1: 98DE80CDE08F0E79A617F52BE15C84C4263FF9B7 | sha256: A44E306755545927B44672353997C788313AE4CD35AEF42040F79F77DACBC310 | sha512: 78F75D4C86FCCABE179EB35D19410B189217FBD95C3F70AEE426B72D56B41CA5C5C26F750B556150D60A24DEB0E5C5601B86AAB81D793C0808660DEA7614D8BB

tools\complete-x64_x64.exe

md5: B4B19B245062248A8AFFE33FAC6B7D37 | sha1: F7C5BA5F1761BA436B4A83BFA21AE9502D517A3A | sha256: 554181480D54CD497F800BE4949B1C5F1DF06FB170F63E1B6FCB55916CEA6136 | sha512: 3EA838B4ACFAB7E2EC4CF21D968AC658B0B9CDB64F57EFFEB59E3EAC7262180F36B20E4E43F239618AEA34B02309FC4A6A78577CCED278F793E188531457031B

tools\chocolateyuninstall.ps1

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

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

tools\chocolateyinstall.ps1

$ErrorActionPreference = 'Stop'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$destDir = Join-Path $toolsDir "vim82"
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('vim82'))) { $destDir = Join-Path $destDir 'vim82' } # Vim will not run if it is not within folder vim82
}

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

Install-ChocolateyPackage @packageArgs
(Get-Item $destdir\patch.exe).LastWriteTime = (Get-Date) # exe must be newer than manifest; Supplied manifest fixes useless UAC request
# Rather than letting the installer place the batch files in C:\WINDOWS, I have included them in this package.
# Installing them in this way ensures the package is compatible with non-admin installs, as a good portable package should :)
Get-ChildItem "$destDir\*.bat" | %{ Install-BinFile -Name $_.BaseName -Path $_ }
Remove-Item -Force -ea 0 "$toolsDir\*_x32.exe","$toolsDir\*_x64.exe"
Write-Host 'Build provided by TuxProject.de - consider donating to help support their server costs.'

Virus Scan Results

VisVim.dll (f522b9acbd38) - ## / 68
diff.exe (4ceceebc8150) - ## / 72
patch.exe (efc277fe48ca) - ## / 72
winpty-agent.exe (9add1a61155e) - ## / 72
winpty.dll (936f611c2129) - ## / 65
winpty-agent.exe (ee44e845e0a6) - ## / 68
winpty.dll (16df8e023ce3) - ## / 71
libsodium.dll (c65f7b4f7c16) - ## / 68
libsodium.dll (e8fc565a7afe) - ## / 68
vim-tux.portable.8.2.3356.nupkg (a1320ca23dc0) - ## / 60
vim-tux.installInstall.exe (554181480d54) - ## / 68
vim-tux.installInstall.exe (a44e30675554) - ## / 65
gvim.exe (bfda1297c57f) - ## / 68
gvimext.dll (f9a9b5aa27b6) - ## / 68
gvim_noOLE.exe (bb22b7fb82c0) - ## / 69
tee.exe (a75a81a648b4) - ## / 69
vim.exe (ba47b978d195) - ## / 69
vim64.dll (2382603aac79) - ## / 66
vimrun.exe (1d87c9aa7d3d) - ## / 69
xxd.exe (6260c81bf6d0) - ## / 69
gvim.exe (e83dda5822e8) - ## / 69
gvim_noOLE.exe (87ed3a512fc2) - ## / 67
tee.exe (2d4830eb997c) - ## / 69
vim.exe (df8a3c02b5c2) - ## / 66
vim32.dll (17b763ed3003) - ## / 68
vimrun.exe (7d2a415a8a03) - ## / 69
xxd.exe (b4987eb611a8) - ## / 68

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

Chocolatey Pro provides runtime protection from possible malware.

Version History

Version	Downloads	Last Updated	Status
Vim Tux (Portable) 9.0.0846	134	Thursday, November 10, 2022	Approved
Vim Tux (Portable) 9.0.0828	34	Friday, November 4, 2022	Approved
Vim Tux (Portable) 9.0.0815	37	Wednesday, October 26, 2022	Approved
Vim Tux (Portable) 9.0.0814	21	Saturday, October 22, 2022	Approved
Vim Tux (Portable) 9.0.0806	22	Friday, October 21, 2022	Approved
Vim Tux (Portable) 9.0.0797	23	Thursday, October 20, 2022	Approved
Vim Tux (Portable) 9.0.0780	30	Tuesday, October 18, 2022	Approved
Vim Tux (Portable) 9.0.0733	33	Thursday, October 13, 2022	Approved
Vim Tux (Portable) 9.0.0715	44	Tuesday, October 11, 2022	Approved
Vim Tux (Portable) 9.0.0682	30	Saturday, October 8, 2022	Approved
Vim Tux (Portable) 9.0.656.20221005	26	Thursday, October 6, 2022	Approved
Vim Tux (Portable) 9.0.0656	26	Wednesday, October 5, 2022	Approved
Vim Tux (Portable) 8.2.3908	255	Monday, December 27, 2021	Approved
Vim Tux (Portable) 8.2.3875	53	Thursday, December 23, 2021	Approved
Vim Tux (Portable) 8.2.3858	55	Tuesday, December 21, 2021	Approved
Vim Tux (Portable) 8.2.3836	52	Saturday, December 18, 2021	Approved
Vim Tux (Portable) 8.2.3811	49	Wednesday, December 15, 2021	Approved
Vim Tux (Portable) 8.2.3794	50	Tuesday, December 14, 2021	Approved
Vim Tux (Portable) 8.2.3763	53	Friday, December 10, 2021	Approved
Vim Tux (Portable) 8.2.3757	44	Wednesday, December 8, 2021	Approved
Vim Tux (Portable) 8.2.3752	46	Tuesday, December 7, 2021	Approved
Vim Tux (Portable) 8.2.3718	56	Friday, December 3, 2021	Approved
Vim Tux (Portable) 8.2.3717	58	Thursday, December 2, 2021	Approved
Vim Tux (Portable) 8.2.3701	46	Tuesday, November 30, 2021	Approved
Vim Tux (Portable) 8.2.3692	51	Monday, November 29, 2021	Approved
Vim Tux (Portable) 8.2.3671	55	Friday, November 26, 2021	Approved
Vim Tux (Portable) 8.2.3659	50	Thursday, November 25, 2021	Approved
Vim Tux (Portable) 8.2.3651	54	Tuesday, November 23, 2021	Approved
Vim Tux (Portable) 8.2.3646	47	Tuesday, November 23, 2021	Approved
Vim Tux (Portable) 8.2.3623	50	Saturday, November 20, 2021	Approved
Vim Tux (Portable) 8.2.3608	58	Thursday, November 18, 2021	Approved
Vim Tux (Portable) 8.2.3595	49	Tuesday, November 16, 2021	Approved
Vim Tux (Portable) 8.2.3579	59	Friday, November 5, 2021	Approved
Vim Tux (Portable) 8.2.3565	59	Wednesday, October 27, 2021	Approved
Vim Tux (Portable) 8.2.3551	52	Friday, October 22, 2021	Approved
Vim Tux (Portable) 8.2.3545	52	Thursday, October 21, 2021	Approved
Vim Tux (Portable) 8.2.3532	44	Tuesday, October 19, 2021	Approved
Vim Tux (Portable) 8.2.3513	64	Saturday, October 16, 2021	Approved
Vim Tux (Portable) 8.2.3505	53	Thursday, October 14, 2021	Approved
Vim Tux (Portable) 8.2.3493	57	Tuesday, October 12, 2021	Approved
Vim Tux (Portable) 8.2.3486	48	Saturday, October 9, 2021	Approved
Vim Tux (Portable) 8.2.3484	51	Thursday, October 7, 2021	Approved
Vim Tux (Portable) 8.2.3478	45	Wednesday, October 6, 2021	Approved
Vim Tux (Portable) 8.2.3469	55	Tuesday, October 5, 2021	Approved
Vim Tux (Portable) 8.2.3458	61	Tuesday, September 28, 2021	Approved
Vim Tux (Portable) 8.2.3455	52	Thursday, September 23, 2021	Approved
Vim Tux (Portable) 8.2.3450	52	Tuesday, September 21, 2021	Approved
Vim Tux (Portable) 8.2.3448	56	Sunday, September 19, 2021	Approved
Vim Tux (Portable) 8.2.3434	62	Tuesday, September 14, 2021	Approved
Vim Tux (Portable) 8.2.3416	56	Thursday, September 9, 2021	Approved
Vim Tux (Portable) 8.2.3394	51	Thursday, September 2, 2021	Approved
Vim Tux (Portable) 8.2.3391	69	Wednesday, September 1, 2021	Approved
Vim Tux (Portable) 8.2.3376	66	Friday, August 27, 2021	Approved
Vim Tux (Portable) 8.2.3358	74	Friday, August 20, 2021	Approved
Vim Tux (Portable) 8.2.3356	54	Wednesday, August 18, 2021	Approved
Vim Tux (Portable) 8.2.3326	98	Wednesday, August 11, 2021	Approved
Vim Tux (Portable) 8.2.3318	64	Monday, August 9, 2021	Approved
Vim Tux (Portable) 8.2.3299	55	Friday, August 6, 2021	Approved
Vim Tux (Portable) 8.2.3290	42	Thursday, August 5, 2021	Approved
Vim Tux (Portable) 8.2.3281	65	Wednesday, August 4, 2021	Approved
Vim Tux (Portable) 8.2.3273	55	Tuesday, August 3, 2021	Approved
Vim Tux (Portable) 8.2.3269	64	Monday, August 2, 2021	Approved
Vim Tux (Portable) 8.2.3263	44	Sunday, August 1, 2021	Approved
Vim Tux (Portable) 8.2.3253	80	Saturday, July 31, 2021	Approved
Vim Tux (Portable) 8.2.3242	55	Thursday, July 29, 2021	Approved
Vim Tux (Portable) 8.2.3223	58	Tuesday, July 27, 2021	Approved
Vim Tux (Portable) 8.2.3204	63	Friday, July 23, 2021	Approved
Vim Tux (Portable) 8.2.3187	56	Tuesday, July 20, 2021	Approved
Vim Tux (Portable) 8.2.3171	65	Friday, July 16, 2021	Approved
Vim Tux (Portable) 8.2.3158	86	Wednesday, July 14, 2021	Approved
Vim Tux (Portable) 8.2.3131	56	Friday, July 9, 2021	Approved
Vim Tux (Portable) 8.2.3120	58	Thursday, July 8, 2021	Approved
Vim Tux (Portable) 8.2.3113	59	Wednesday, July 7, 2021	Approved
Vim Tux (Portable) 8.2.3107	55	Tuesday, July 6, 2021	Approved
Vim Tux (Portable) 8.2.3104	58	Monday, July 5, 2021	Approved
Vim Tux (Portable) 8.2.3095	58	Sunday, July 4, 2021	Approved
Vim Tux (Portable) 8.2.3080	59	Thursday, July 1, 2021	Approved
Vim Tux (Portable) 8.2.3075	53	Wednesday, June 30, 2021	Approved
Vim Tux (Portable) 8.2.3066	68	Monday, June 28, 2021	Approved
Vim Tux (Portable) 8.2.3055	57	Sunday, June 27, 2021	Approved
Vim Tux (Portable) 8.2.3043	58	Thursday, June 24, 2021	Approved
Vim Tux (Portable) 8.2.3033	66	Tuesday, June 22, 2021	Approved
Vim Tux (Portable) 8.2.3020	49	Sunday, June 20, 2021	Approved
Vim Tux (Portable) 8.2.3017	66	Friday, June 18, 2021	Approved
Vim Tux (Portable) 8.2.2840	110	Saturday, May 8, 2021	Approved
Vim Tux (Portable) 8.2.2832	71	Wednesday, May 5, 2021	Approved
Vim Tux (Portable) 8.2.2815	84	Wednesday, April 28, 2021	Approved
Vim Tux (Portable) 8.2.2799	84	Thursday, April 22, 2021	Approved
Vim Tux (Portable) 8.2.2794	57	Wednesday, April 21, 2021	Approved
Vim Tux (Portable) 8.2.2763	76	Thursday, April 15, 2021	Approved
Vim Tux (Portable) 8.2.2738	75	Friday, April 9, 2021	Approved
Vim Tux (Portable) 8.2.2730	72	Wednesday, April 7, 2021	Approved
Vim Tux (Portable) 8.2.2679	71	Wednesday, March 31, 2021	Approved
Vim Tux (Portable) 8.2.2650	72	Friday, March 26, 2021	Approved
Vim Tux (Portable) 8.2.2648	80	Wednesday, March 24, 2021	Approved
Vim Tux (Portable) 8.2.2637	73	Tuesday, March 23, 2021	Approved
Vim Tux (Portable) 8.2.2491	146	Thursday, February 11, 2021	Approved
Vim Tux (Portable) 8.2.2129	145	Saturday, December 12, 2020	Approved
Vim Tux (Portable) 8.2.1981	101	Saturday, November 14, 2020	Approved
Vim Tux (Portable) 8.2.1955	112	Friday, November 6, 2020	Approved
Vim Tux (Portable) 8.2.1923	108	Friday, October 30, 2020	Approved
Vim Tux (Portable) 8.2.1883	107	Thursday, October 22, 2020	Approved
Vim Tux (Portable) 8.2.1858	94	Sunday, October 18, 2020	Approved
Vim Tux (Portable) 8.2.1738	130	Friday, September 25, 2020	Approved
Vim Tux (Portable) 8.2.1651	118	Thursday, September 10, 2020	Approved
Vim Tux (Portable) 8.2.1058	197	Friday, June 26, 2020	Approved
Vim Tux (Portable) 8.2.1007	117	Friday, June 19, 2020	Approved
Vim Tux (Portable) 8.2.988	155	Wednesday, June 17, 2020	Approved
Vim Tux (Portable) 8.2.960	127	Friday, June 12, 2020	Approved
Vim Tux (Portable) 8.2.950	115	Thursday, June 11, 2020	Approved
Vim Tux (Portable) 8.2.916	143	Sunday, June 7, 2020	Approved
Vim Tux (Portable) 8.2.882	120	Tuesday, June 2, 2020	Approved
Vim Tux (Portable) 8.2.855	112	Sunday, May 31, 2020	Approved
Vim Tux (Portable) 8.2.834	129	Friday, May 29, 2020	Approved
Vim Tux (Portable) 8.2.829	148	Wednesday, May 27, 2020	Approved
Vim Tux (Portable) 8.2.821	113	Tuesday, May 26, 2020	Approved
Vim Tux (Portable) 8.2.806	121	Friday, May 22, 2020	Approved
Vim Tux (Portable) 8.2.803	106	Thursday, May 21, 2020	Approved
Vim Tux (Portable) 8.2.766	147	Sunday, May 17, 2020	Approved
Vim Tux (Portable) 8.2.750	116	Thursday, May 14, 2020	Approved
Vim Tux (Portable) 8.2.735	124	Tuesday, May 12, 2020	Approved
Vim Tux (Portable) 8.2.647	189	Monday, April 27, 2020	Approved
Vim Tux (Portable) 8.2.640	114	Sunday, April 26, 2020	Approved
Vim Tux (Portable) 8.2.625	119	Friday, April 24, 2020	Approved
Vim Tux (Portable) 8.2.612	186	Tuesday, April 21, 2020	Approved
Vim Tux (Portable) 8.2.592	138	Saturday, April 18, 2020	Approved
Vim Tux (Portable) 8.2.585	123	Friday, April 17, 2020	Approved
Vim Tux (Portable) 8.2.577	144	Tuesday, April 14, 2020	Approved
Vim Tux (Portable) 8.2.0536	134	Sunday, April 12, 2020	Approved
Vim Tux (Portable) 8.2.0515	144	Monday, April 6, 2020	Approved
Vim Tux (Portable) 8.2.0505	145	Saturday, April 4, 2020	Approved
Vim Tux (Portable) 8.2.0486	131	Wednesday, April 1, 2020	Approved
Vim Tux (Portable) 8.2.0464	144	Sunday, March 29, 2020	Approved
Vim Tux (Portable) 8.2.0397	156	Wednesday, March 18, 2020	Approved
Vim Tux (Portable) 8.2.0369	159	Wednesday, March 11, 2020	Approved
Vim Tux (Portable) 8.2.0357	148	Friday, March 6, 2020	Approved
Vim Tux (Portable) 8.2.0324	174	Friday, February 28, 2020	Approved
Vim Tux (Portable) 8.2.0313	133	Monday, February 24, 2020	Approved
Vim Tux (Portable) 8.2.0294	123	Saturday, February 22, 2020	Approved
Vim Tux (Portable) 8.2.0285	125	Friday, February 21, 2020	Approved
Vim Tux (Portable) 8.2.0273	140	Tuesday, February 18, 2020	Approved
Vim Tux (Portable) 8.2.0231	166	Sunday, February 9, 2020	Approved
Vim Tux (Portable) 8.2.0164	153	Wednesday, January 29, 2020	Approved
Vim Tux (Portable) 8.2.0147	105	Saturday, January 25, 2020	Approved
Vim Tux (Portable) 8.2.0129	172	Sunday, January 19, 2020	Approved
Vim Tux (Portable) 8.2.0114	136	Tuesday, January 14, 2020	Approved
Vim Tux (Portable) 8.2.0109	134	Friday, January 10, 2020	Approved
Vim Tux (Portable) 8.2.0092	145	Tuesday, January 7, 2020	Approved
Vim Tux (Portable) 8.2.0080	153	Friday, January 3, 2020	Approved
Vim Tux (Portable) 8.2.0065	135	Tuesday, December 31, 2019	Approved
Vim Tux (Portable) 8.2.0055	112	Monday, December 30, 2019	Approved
Vim Tux (Portable) 8.2.0052	119	Sunday, December 29, 2019	Approved
Vim Tux (Portable) 8.2.0033	127	Tuesday, December 24, 2019	Approved
Vim Tux (Portable) 8.2.0021	126	Thursday, December 19, 2019	Approved
Vim Tux (Portable) 8.2.0011	147	Monday, December 16, 2019	Approved
Vim Tux (Portable) 8.1.2333	189	Friday, November 22, 2019	Approved
Vim Tux (Portable) 8.1.2323	168	Thursday, November 21, 2019	Approved
Vim Tux (Portable) 8.1.2311	172	Sunday, November 17, 2019	Approved
Vim Tux (Portable) 8.1.2300	150	Thursday, November 14, 2019	Approved
Vim Tux (Portable) 8.1.2237	181	Friday, November 1, 2019	Approved
Vim Tux (Portable) 8.1.2204	214	Thursday, October 24, 2019	Approved
Vim Tux (Portable) 8.1.2200	165	Wednesday, October 23, 2019	Approved
Vim Tux (Portable) 8.1.2148	171	Monday, October 14, 2019	Approved
Vim Tux (Portable) 8.1.2133	140	Friday, October 11, 2019	Approved
Vim Tux (Portable) 8.1.2117	170	Sunday, October 6, 2019	Approved
Vim Tux (Portable) 8.1.2108	162	Thursday, October 3, 2019	Approved
Vim Tux (Portable) 8.1.2103	130	Tuesday, October 1, 2019	Approved
Vim Tux (Portable) 8.1.2079	175	Friday, September 27, 2019	Approved
Vim Tux (Portable) 8.1.2071	132	Wednesday, September 25, 2019	Approved
Vim Tux (Portable) 8.1.2052	148	Thursday, September 19, 2019	Approved
Vim Tux (Portable) 8.1.2019	188	Tuesday, September 10, 2019	Approved
Vim Tux (Portable) 8.1.2004	150	Sunday, September 8, 2019	Approved
Vim Tux (Portable) 8.1.1995	125	Saturday, September 7, 2019	Approved
Vim Tux (Portable) 8.1.1986	151	Thursday, September 5, 2019	Approved
Vim Tux (Portable) 8.1.1961	143	Monday, September 2, 2019	Approved
Vim Tux (Portable) 8.1.1927	178	Monday, August 26, 2019	Approved
Vim Tux (Portable) 8.1.1915	144	Saturday, August 24, 2019	Approved
Vim Tux (Portable) 8.1.1906	159	Thursday, August 22, 2019	Approved
Vim Tux (Portable) 8.1.1890	136	Tuesday, August 20, 2019	Approved
Vim Tux (Portable) 8.1.1836	199	Sunday, August 11, 2019	Approved
Vim Tux (Portable) 8.1.1813	178	Monday, August 5, 2019	Approved
Vim Tux (Portable) 8.1.1744	163	Thursday, July 25, 2019	Approved
Vim Tux (Portable) 8.1.1729	165	Tuesday, July 23, 2019	Approved
Vim Tux (Portable) 8.1.1713	164	Friday, July 19, 2019	Approved
Vim Tux (Portable) 8.1.1695	151	Tuesday, July 16, 2019	Approved
Vim Tux (Portable) 8.1.1669	149	Saturday, July 13, 2019	Approved
Vim Tux (Portable) 8.1.1655	184	Tuesday, July 9, 2019	Approved
Vim Tux (Portable) 8.1.1631	136	Friday, July 5, 2019	Approved
Vim Tux (Portable) 8.1.1601	197	Thursday, June 27, 2019	Approved
Vim Tux (Portable) 8.1.1578	169	Saturday, June 22, 2019	Approved
Vim Tux (Portable) 8.1.1573	172	Thursday, June 20, 2019	Approved
Vim Tux (Portable) 8.1.1566	150	Tuesday, June 18, 2019	Approved
Vim Tux (Portable) 8.1.1557	157	Monday, June 17, 2019	Approved
Vim Tux (Portable) 8.1.1536	138	Sunday, June 16, 2019	Approved
Vim Tux (Portable) 8.1.1523	172	Friday, June 14, 2019	Approved
Vim Tux (Portable) 8.1.1515	185	Tuesday, June 11, 2019	Approved
Vim Tux (Portable) 8.1.1511	169	Monday, June 10, 2019	Approved
Vim Tux (Portable) 8.1.1455	161	Monday, June 3, 2019	Approved
Vim Tux (Portable) 8.1.1432	191	Friday, May 31, 2019	Approved
Vim Tux (Portable) 8.1.1413	181	Tuesday, May 28, 2019	Approved
Vim Tux (Portable) 8.1.1373	189	Friday, May 24, 2019	Approved
Vim Tux (Portable) 8.1.1364	165	Thursday, May 23, 2019	Approved
Vim Tux (Portable) 8.1.1353	150	Monday, May 20, 2019	Approved
Vim Tux (Portable) 8.1.1333	173	Thursday, May 16, 2019	Approved
Vim Tux (Portable) 8.1.1328	160	Monday, May 13, 2019	Approved
Vim Tux (Portable) 8.1.1312	141	Saturday, May 11, 2019	Approved
Vim Tux (Portable) 8.1.1298	177	Thursday, May 9, 2019	Approved
Vim Tux (Portable) 8.1.1286	188	Tuesday, May 7, 2019	Approved
Vim Tux (Portable) 8.1.1197	185	Monday, April 22, 2019	Approved
Vim Tux (Portable) 8.1.1183	174	Thursday, April 18, 2019	Approved
Vim Tux (Portable) 8.1.1165	173	Sunday, April 14, 2019	Approved
Vim Tux (Portable) 8.1.1140	169	Tuesday, April 9, 2019	Approved
Vim Tux (Portable) 8.1.1136	159	Monday, April 8, 2019	Approved
Vim Tux (Portable) 8.1.1124	157	Sunday, April 7, 2019	Approved
Vim Tux (Portable) 8.1.1103	186	Thursday, April 4, 2019	Approved
Vim Tux (Portable) 8.1.1097	189	Monday, April 1, 2019	Approved
Vim Tux (Portable) 8.1.1073	138	Saturday, March 30, 2019	Approved
Vim Tux (Portable) 8.1.1057	193	Thursday, March 28, 2019	Approved
Vim Tux (Portable) 8.1.1032	210	Friday, March 22, 2019	Approved
Vim Tux (Portable) 8.1.1027	174	Thursday, March 21, 2019	Approved
Vim Tux (Portable) 8.1.1017	134	Tuesday, March 19, 2019	Approved
Vim Tux (Portable) 8.1.1004	175	Monday, March 11, 2019	Approved
Vim Tux (Portable) 8.1.998	156	Friday, March 8, 2019	Approved
Vim Tux (Portable) 8.1.990	189	Sunday, March 3, 2019	Approved
Vim Tux (Portable) 8.1.984	149	Thursday, February 28, 2019	Approved
Vim Tux (Portable) 8.1.978	156	Saturday, February 23, 2019	Approved
Vim Tux (Portable) 8.1.966	173	Friday, February 22, 2019	Approved
Vim Tux (Portable) 8.1.947	153	Tuesday, February 19, 2019	Approved
Vim Tux (Portable) 8.1.934	118	Sunday, February 17, 2019	Approved
Vim Tux (Portable) 8.1.926	162	Saturday, February 16, 2019	Approved
Vim Tux (Portable) 8.1.909	145	Thursday, February 14, 2019	Approved
Vim Tux (Portable) 8.1.895	170	Tuesday, February 12, 2019	Approved
Vim Tux (Portable) 8.1.0885	177	Sunday, February 10, 2019	Approved
Vim Tux (Portable) 8.1.0877	182	Thursday, February 7, 2019	Approved
Vim Tux (Portable) 8.1.0871	188	Monday, February 4, 2019	Approved
Vim Tux (Portable) 8.1.0868	179	Sunday, February 3, 2019	Approved
Vim Tux (Portable) 8.1.0865	152	Saturday, February 2, 2019	Approved
Vim Tux (Portable) 8.1.0842	174	Thursday, January 31, 2019	Approved
Vim Tux (Portable) 8.1.0837	199	Monday, January 28, 2019	Approved
Vim Tux (Portable) 8.1.0814	171	Friday, January 25, 2019	Approved
Vim Tux (Portable) 8.1.0796	162	Thursday, January 24, 2019	Approved
Vim Tux (Portable) 8.1.0788	156	Tuesday, January 22, 2019	Approved
Vim Tux (Portable) 8.1.0757	199	Thursday, January 17, 2019	Approved
Vim Tux (Portable) 8.1.0749	147	Tuesday, January 15, 2019	Approved
Vim Tux (Portable) 8.1.0727	144	Saturday, January 12, 2019	Approved
Vim Tux (Portable) 8.1.0712	208	Thursday, January 10, 2019	Approved
Vim Tux (Portable) 8.1.0700	162	Tuesday, January 8, 2019	Approved
Vim Tux (Portable) 8.1.0690	225	Saturday, January 5, 2019	Approved
Vim Tux (Portable) 8.1.0681	203	Thursday, January 3, 2019	Approved
Vim Tux (Portable) 8.1.0674	171	Wednesday, January 2, 2019	Approved
Vim Tux (Portable) 8.1.0647	210	Friday, December 28, 2018	Approved
Vim Tux (Portable) 8.1.0644	171	Thursday, December 27, 2018	Approved
Vim Tux (Portable) 8.1.0635	140	Wednesday, December 26, 2018	Approved
Vim Tux (Portable) 8.1.0630	182	Tuesday, December 25, 2018	Approved
Vim Tux (Portable) 8.1.0629	161	Monday, December 24, 2018	Approved
Vim Tux (Portable) 8.1.0622	147	Sunday, December 23, 2018	Approved
Vim Tux (Portable) 8.1.0617	186	Saturday, December 22, 2018	Approved
Vim Tux (Portable) 8.1.0594	163	Sunday, December 16, 2018	Approved
Vim Tux (Portable) 8.1.0577	189	Thursday, December 13, 2018	Approved
Vim Tux (Portable) 8.1.0551	196	Friday, November 30, 2018	Approved
Vim Tux (Portable) 8.1.0547	179	Monday, November 26, 2018	Approved
Vim Tux (Portable) 8.1.0536	171	Tuesday, November 20, 2018	Approved
Vim Tux (Portable) 8.1.0524	182	Tuesday, November 13, 2018	Approved
Vim Tux (Portable) 8.1.0513	196	Thursday, November 8, 2018	Approved
Vim Tux (Portable) 8.1.0509	180	Sunday, November 4, 2018	Approved
Vim Tux (Portable) 8.1.0498	171	Sunday, October 28, 2018	Approved
Vim Tux (Portable) 8.1.0489	196	Monday, October 22, 2018	Approved
Vim Tux (Portable) 8.1.0474	202	Monday, October 15, 2018	Approved
Vim Tux (Portable) 8.1.0470	199	Friday, October 12, 2018	Approved
Vim Tux (Portable) 8.1.0451	221	Friday, October 5, 2018	Approved
Vim Tux (Portable) 8.1.0442	196	Monday, October 1, 2018	Approved
Vim Tux (Portable) 8.1.0436	171	Thursday, September 27, 2018	Approved
Vim Tux (Portable) 8.1.0425	182	Saturday, September 22, 2018	Approved
Vim Tux (Portable) 8.1.0408	186	Thursday, September 20, 2018	Approved
Vim Tux (Portable) 8.1.0401	169	Tuesday, September 18, 2018	Approved
Vim Tux (Portable) 8.1.0385	214	Friday, September 14, 2018	Approved
Vim Tux (Portable) 8.1.0371	192	Thursday, September 13, 2018	Approved
Vim Tux (Portable) 8.1.0362	184	Tuesday, September 11, 2018	Approved
Vim Tux (Portable) 8.1.0354	197	Sunday, September 9, 2018	Approved
Vim Tux (Portable) 8.1.0347	188	Thursday, September 6, 2018	Approved
Vim Tux (Portable) 8.1.0342	181	Sunday, September 2, 2018	Approved
Vim Tux (Portable) 8.1.0332	174	Thursday, August 30, 2018	Approved
Vim Tux (Portable) 8.1.0327	179	Sunday, August 26, 2018	Approved
Vim Tux (Portable) 8.1.0318	180	Thursday, August 23, 2018	Approved
Vim Tux (Portable) 8.1.0301	183	Tuesday, August 21, 2018	Approved
Vim Tux (Portable) 8.1.0297	192	Monday, August 20, 2018	Approved
Vim Tux (Portable) 8.1.0288	220	Thursday, August 16, 2018	Approved
Vim Tux (Portable) 8.1.0278	200	Monday, August 13, 2018	Approved
Vim Tux (Portable) 8.1.0271	184	Sunday, August 12, 2018	Approved
Vim Tux (Portable) 8.1.0259	222	Friday, August 10, 2018	Approved
Vim Tux (Portable) 8.1.0239	218	Sunday, August 5, 2018	Approved
Vim Tux (Portable) 8.1.0229	201	Tuesday, July 31, 2018	Approved
Vim Tux (Portable) 8.1.0221	203	Sunday, July 29, 2018	Approved
Vim Tux (Portable) 8.1.0210	188	Thursday, July 26, 2018	Approved
Vim Tux (Portable) 8.1.0207	189	Tuesday, July 24, 2018	Approved
Vim Tux (Portable) 8.1.0203	204	Monday, July 23, 2018	Approved
Vim Tux (Portable) 8.1.0199	196	Saturday, July 21, 2018	Approved
Vim Tux (Portable) 8.1.0196	224	Friday, July 20, 2018	Approved
Vim Tux (Portable) 8.1.0191	168	Tuesday, July 17, 2018	Approved
Vim Tux (Portable) 8.1.0186	206	Sunday, July 15, 2018	Approved
Vim Tux (Portable) 8.1.0173	259	Tuesday, July 10, 2018	Approved
Vim Tux (Portable) 8.1.0153	228	Friday, July 6, 2018	Approved
Vim Tux (Portable) 8.1.0138	227	Tuesday, July 3, 2018	Approved
Vim Tux (Portable) 8.1.0133	190	Sunday, July 1, 2018	Approved
Vim Tux (Portable) 8.1.0126	213	Friday, June 29, 2018	Approved
Vim Tux (Portable) 8.1.0105	217	Sunday, June 24, 2018	Approved
Vim Tux (Portable) 8.1.0054	247	Thursday, June 14, 2018	Approved
Vim Tux (Portable) 8.1.0034	234	Tuesday, June 5, 2018	Approved
Vim Tux (Portable) 8.1.0022	231	Friday, May 25, 2018	Approved
Vim Tux (Portable) 8.1.0013	255	Tuesday, May 22, 2018	Approved
Vim Tux (Portable) 8.1.0009	221	Monday, May 21, 2018	Approved
Vim Tux (Portable) 8.1.0004	213	Sunday, May 20, 2018	Approved
Vim Tux (Portable) 8.1.0.20180519	241	Saturday, May 19, 2018	Approved
Vim Tux (Portable) 8.1.0000	236	Friday, May 18, 2018	Approved
Vim Tux (Portable) 8.0.1848	282	Thursday, May 17, 2018	Approved
Vim Tux (Portable) 8.0.1831	242	Monday, May 14, 2018	Approved
Vim Tux (Portable) 8.0.1820	232	Sunday, May 13, 2018	Approved
Vim Tux (Portable) 8.0.1806	258	Thursday, May 10, 2018	Approved
Vim Tux (Portable) 8.0.1799	215	Monday, May 7, 2018	Approved
Vim Tux (Portable) 8.0.1794	225	Sunday, May 6, 2018	Approved
Vim Tux (Portable) 8.0.1790	268	Friday, May 4, 2018	Approved
Vim Tux (Portable) 8.0.1788	242	Thursday, May 3, 2018	Approved
Vim Tux (Portable) 8.0.1774	295	Monday, April 30, 2018	Approved
Vim Tux (Portable) 8.0.1765	244	Thursday, April 26, 2018	Approved
Vim Tux (Portable) 8.0.1748	234	Sunday, April 22, 2018	Approved
Vim Tux (Portable) 8.0.1736	253	Friday, April 20, 2018	Approved
Vim Tux (Portable) 8.0.1727	235	Wednesday, April 18, 2018	Approved
Vim Tux (Portable) 8.0.1705	233	Saturday, April 14, 2018	Approved
Vim Tux (Portable) 8.0.1679	246	Monday, April 9, 2018	Approved
Vim Tux (Portable) 8.0.1664	241	Saturday, April 7, 2018	Approved
Vim Tux (Portable) 8.0.1655	250	Saturday, March 31, 2018	Approved
Vim Tux (Portable) 8.0.1638	285	Sunday, March 25, 2018	Approved
Vim Tux (Portable) 8.0.1626	354	Thursday, March 22, 2018	Approved
Vim Tux (Portable) 8.0.1612	267	Saturday, March 17, 2018	Approved
Vim Tux (Portable) 8.0.1601	263	Tuesday, March 13, 2018	Approved
Vim Tux (Portable) 8.0.1591	294	Friday, March 9, 2018	Approved
Vim Tux (Portable) 8.0.1563	263	Sunday, March 4, 2018	Approved
Vim Tux (Portable) 8.0.1553	281	Friday, March 2, 2018	Approved
Vim Tux (Portable) 8.0.1532	290	Sunday, February 25, 2018	Approved
Vim Tux (Portable) 8.0.1504	291	Thursday, February 15, 2018	Approved
Vim Tux (Portable) 8.0.1473	277	Thursday, February 8, 2018	Approved
Vim Tux (Portable) 8.0.1451	297	Saturday, February 3, 2018	Approved
Vim Tux (Portable) 8.0.1438	299	Tuesday, January 30, 2018	Approved
Vim Tux (Portable) 8.0.1431	289	Saturday, January 27, 2018	Approved
Vim Tux (Portable) 8.0.1428	347	Thursday, January 4, 2018	Approved
Vim Tux (Portable) 8.0.1422	308	Saturday, December 30, 2017	Approved
Vim Tux (Portable) 8.0.1390	303	Sunday, December 17, 2017	Approved
Vim Tux (Portable) 8.0.1379	280	Thursday, December 14, 2017	Approved
Vim Tux (Portable) 8.0.1376	332	Thursday, December 7, 2017	Approved
Vim Tux (Portable) 8.0.1358	330	Friday, December 1, 2017	Approved
Vim Tux (Portable) 8.0.1330	316	Thursday, November 23, 2017	Approved
Vim Tux (Portable) 8.0.1311	287	Monday, November 20, 2017	Approved
Vim Tux (Portable) 8.0.1305	263	Saturday, November 18, 2017	Approved
Vim Tux (Portable) 8.0.1272	371	Thursday, November 9, 2017	Approved
Vim Tux (Portable) 8.0.1257	288	Sunday, November 5, 2017	Approved
Vim Tux (Portable) 8.0.1203	353	Wednesday, October 18, 2017	Approved
Vim Tux (Portable) 8.0.1157	359	Friday, September 29, 2017	Approved
Vim Tux (Portable) 8.0.1088	324	Monday, September 11, 2017	Approved
Vim Tux (Portable) 8.0.1010	343	Tuesday, August 29, 2017	Approved
Vim Tux (Portable) 8.0.0987	307	Wednesday, August 23, 2017	Approved
Vim Tux (Portable) 8.0.0737	382	Thursday, July 20, 2017	Approved
Vim Tux (Portable) 8.0.0642	353	Sunday, June 18, 2017	Approved
Vim Tux (Portable) 8.0.0584	375	Wednesday, April 26, 2017	Approved
Vim Tux (Portable) 8.0.0566	292	Friday, April 21, 2017	Approved
Vim Tux (Portable) 8.0.0123	576	Friday, December 9, 2016	Approved
Vim Tux (Portable) 8.0.0117	393	Friday, December 2, 2016	Approved
Vim Tux (Portable) 8.0.0066	375	Thursday, November 10, 2016	Approved
Vim Tux (Portable) 8.0.0051	393	Friday, October 28, 2016	Approved
Vim Tux (Portable) 8.0.0045	414	Friday, October 21, 2016	Approved
Vim Tux (Portable) 8.0.0017	319	Wednesday, September 28, 2016	Approved
Vim Tux (Portable) 8.0.005	412	Friday, September 16, 2016	Approved
Vim Tux (Portable) 7.4.2222	417	Thursday, August 18, 2016	Approved
Vim Tux (Portable) 7.4.2180	371	Tuesday, August 9, 2016	Approved
Vim Tux (Portable) 7.4.2153	366	Friday, August 5, 2016	Approved
Vim Tux (Portable) 7.4.2089	370	Friday, July 22, 2016	Approved
Vim Tux (Portable) 7.4.2034	370	Friday, July 15, 2016	Approved
Vim Tux (Portable) 7.4.1987	372	Sunday, July 3, 2016	Approved
Vim Tux (Portable) 7.4.1949	370	Thursday, June 23, 2016	Approved
Vim Tux (Portable) 7.4.1913	376	Friday, June 10, 2016	Approved
Vim Tux (Portable) 7.4.1905	328	Thursday, June 9, 2016	Approved
Vim Tux (Portable) 7.4.1901	374	Tuesday, June 7, 2016	Approved
Vim Tux (Portable) 7.4.1862	289	Thursday, June 2, 2016	Approved
Vim Tux (Portable) 7.4.1856	345	Monday, May 30, 2016	Approved
Vim Tux (Portable) 7.4.1848	346	Friday, May 27, 2016	Approved
Vim Tux (Portable) 7.4.1842	331	Thursday, May 26, 2016	Approved
Vim Tux (Portable) 7.4.1832	314	Thursday, May 19, 2016	Approved
Vim Tux (Portable) 7.4.1829	412	Thursday, May 12, 2016	Approved
Vim Tux (Portable) 7.4.1824	383	Monday, May 9, 2016	Approved

Release Notes

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

Dependencies

- vcredist2015

Discussion for the Vim Tux (Portable) Package

Ground Rules:

This discussion is only about Vim Tux (Portable) and the Vim Tux (Portable) package. If you have feedback for Chocolatey, please contact the Google Group.
This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
Tell us what you love about the package or Vim Tux (Portable), or tell us what needs improvement.
Share your experiences with the package, or extra configuration or gotchas that you've found.
If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.

Resources

Events

Courses

68,163

54

18 Aug 2021

Vim Tux (Portable)

Vim Tux (Portable) 8.2.3356

Some Checks Have Failed or Are Not Yet Complete

Deployment Method: Individual Install, Upgrade, & Uninstall

Deployment Method:

1. Enter Your Internal Repository Url

2. Setup Your Environment

1. Ensure you are set for organizational deployment

2. Get the package into your environment

3. Copy Your Script

4. If applicable - Chocolatey configuration/installation

Ground Rules: