Downloads of v 2.2.7:


Last Update:

11 Aug 2022

Package Maintainer(s):

Software Author(s):

  • crhodes
  • demoss
  • jsnell
  • pkhuong
  • and 4 others


sbcl commonlisp lisp compiler interpreter runtime programming

sbcl (Install)

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

  • 1
  • 2
  • 3

2.2.7 | Updated: 11 Aug 2022



Downloads of v 2.2.7:



Software Author(s):

  • crhodes
  • demoss
  • jsnell
  • pkhuong
  • and 4 others

  • 1
  • 2
  • 3
sbcl (Install) 2.2.7

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

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

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


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


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


Deployment Method:

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

1. Enter Your Internal Repository Url

(this should look similar to

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

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

3. Copy Your Script

choco upgrade sbcl -y --source="'INTERNAL REPO URL'" --version="'2.2.7'" [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 sbcl -y --source="'INTERNAL REPO URL'" --version="'2.2.7'" 

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

Exit $exitCode

- name: Install sbcl
    name: sbcl
    version: '2.2.7'
    state: present

See docs at

chocolatey_package 'sbcl' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '2.2.7'

See docs at

cChocoPackageInstaller sbcl
    Name     = "sbcl"
    Version  = "2.2.7"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'sbcl':
  ensure   => '2.2.7',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

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

This package was approved as a trusted package on 11 Aug 2022.


Steel Bank Common Lisp (SBCL) is a high performance Common Lisp
compiler. It is open source / free software, with a permissive license.
In addition to the compiler and runtime system for ANSI Common Lisp, it
provides an interactive environment including a debugger, a statistical
profiler, a code coverage tool, and many other extensions.

$ErrorActionPreference = 'Stop'; # stop on all errors
$toolsDir   = Split-Path -parent $MyInvocation.MyCommand.Definition

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  fileType      = 'MSI'
  url           = ''
  softwareName  = 'Steel Bank Common Lisp*'
  checksum      = '82dfc14f9915da88138eff0910fd7c9009a643fc115ab3f8458753fe38d14ebf'
  checksumType  = 'sha256'

  # MSI
  silentArgs    = "/qn /norestart /l*v `"$($env:TEMP)\$($packageName).$($env:chocolateyPackageVersion).MsiInstall.log`""

Install-ChocolateyPackage @packageArgs

$sbclhome = Join-Path ([environment]::GetFolderPath([environment+specialfolder]::ProgramFiles)) `
                      -ChildPath 'Steel Bank Common Lisp'

$target = Join-Path $sbclhome -ChildPath 'sbcl.exe'
$icon = Join-Path $toolsDir -ChildPath 'sbcl.ico'
$shortcut = Join-Path ([environment]::GetFolderPath([environment+specialfolder]::Programs)) -ChildPath 'sbcl.lnk'
Install-ChocolateyShortcut -ShortcutFilePath $shortcut `
                           -Targetpath $target `
                           -IconLocation $icon `
                           -WorkingDirectory ([environment]::GetFolderPath([environment+specialfolder]::UserProfile))`
                           -Description 'Steel Bank Common Lisp (SBCL)'

Install-ChocolateyEnvironmentVariable -variableName "SBCL_HOME" -variableValue $sbclhome -variableType 'Machine'

## Set up a file association
## -

Install-BinFile -Name 'sbcl' -path $target
$ErrorActionPreference = 'Stop';
$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  softwareName  = 'Steel Bank Common Lisp*'
  fileType      = 'MSI'
  # MSI
  silentArgs    = "/qn /norestart"
  validExitCodes= @(0, 3010, 1605, 1614, 1641) #

[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']

if ($key.Count -eq 1) {
  $key | % {
    $packageArgs['file'] = "$($_.UninstallString)"

    if ($packageArgs['fileType'] -eq 'MSI') {
      $packageArgs['silentArgs'] = "$($_.PSChildName) $($packageArgs['silentArgs'])"
      $packageArgs['file'] = ''

    Uninstall-ChocolateyPackage @packageArgs
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$($key.Count) matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | % {Write-Warning "- $($_.DisplayName)"}

$sbclhome = $env:SBCL_HOME
$target = join-Path $sbclhome 'sbcl.exe'
Uninstall-ChocolateyEnvironmentVariable -VariableName 'SBCL_HOME' -VariableType 'Machine'
Uninstall-BinFile -Name 'sbcl' -Path $target

$shortcut = Join-Path ([environment]::GetFolderPath([environment+specialfolder]::Programs)) -ChildPath 'sbcl.lnk'
Remove-Item $shortcut -Force

Log in or click on link to see number of positives.

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.

Add to Builder Version Downloads Last Updated Status
sbcl (Install) 2.2.7 83 Thursday, August 11, 2022 Approved
sbcl (Install) 2.2.6 96 Monday, July 11, 2022 Approved
sbcl (Install) 2.2.5 147 Tuesday, May 31, 2022 Approved
sbcl (Install) 2.2.4 107 Sunday, May 1, 2022 Approved
sbcl (Install) 2.2.3 90 Thursday, March 31, 2022 Approved
sbcl (Install) 2.2.2 74 Tuesday, March 8, 2022 Approved
sbcl (Install) 2.2.1 111 Sunday, February 6, 2022 Approved
sbcl (Install) 2.2.0 49 Thursday, January 13, 2022 Approved
sbcl (Install) 2.1.11 103 Saturday, December 4, 2021 Approved
Discussion for the sbcl (Install) Package

Ground Rules:

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