Downloads:
729,665
Downloads of v 3.10.3.0:
10
Last Update:
17 Jul 2024
Published Date:
17 Jul 2024
Package Maintainer(s):
Software Author(s):
- Cabal Team
Tags:
cabal ghc haskellCabal
(Waiting for Maintainer to take corrective action)
- 1
- 2
- 3
3.10.3.0 | Updated: 17 Jul 2024
Downloads:
729,665
Downloads of v 3.10.3.0:
10
Published:
17 Jul 2024
Maintainer(s):
Software Author(s):
- Cabal Team
Cabal 3.10.3.0
(Waiting for Maintainer to take corrective action)
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
This version is in moderation and has not yet been approved. This means it doesn't show up under normal search.
- Until approved, you should consider this package version unsafe - it could do very bad things to your system (it probably doesn't but you have been warned, that's why we have moderation).
- This package version can change wildly over the course of moderation until it is approved. If you install it and it later has changes to this version, you will be out of sync with any changes that have been made to the package. Until approved, you should consider that this package version doesn't even exist.
- You cannot install this package under normal scenarios. See How to install package version under moderation for more information.
- There are also no guarantees that it will be approved.
There are versions of this package awaiting moderation (possibly just this one). See the Version History section below.
The 'cabal.exe' command-line program simplifies the process of managing Haskell software by automating the fetching, configuration, compilation and installation of Haskell libraries and programs.
Cabal is a system for building and packaging Haskell libraries and programs. It defines a common interface for package authors and distributors to easily build their applications in a portable way. Cabal is part of a larger infrastructure for distributing, organizing, and cataloging Haskell libraries and programs.
Specifically, the Cabal describes what a Haskell package is, how these packages interact with the language, and what Haskell implementations must to do to support packages. The Cabal also specifies some infrastructure (code) that makes it easy for tool authors to build and distribute conforming packages.
The Cabal is only one contribution to the larger goal. In particular, the Cabal says nothing about more global issues such as how authors decide where in the module name space their library should live; how users can find a package they want; how orphan packages find new owners; and so on.
Copyright (c) 2003-2023, Cabal Development Team.
See the AUTHORS file for the full list of copyright holders.
See */LICENSE for the copyright holders of the subcomponents.
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided
with the distribution.
* Neither the name of Isaac Jones nor the names of other
contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
$version = '3.10.3.0'
$packageName = 'cabal'
$url = 'https://downloads.haskell.org/cabal/cabal-install-3.2.0.0/cabal-install-3.2.0.0-i386-unknown-mingw32.zip'
$url64 = 'https://downloads.haskell.org/cabal/cabal-install-3.10.3.0/cabal-install-3.10.3.0-x86_64-windows.zip'
$binRoot = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
$packageFullName = Join-Path $binRoot ($packageName + '-' + $version)
$is64 = (Get-OSArchitectureWidth 64) -and $env:chocolateyForceX86 -ne 'true'
$cabal = Join-Path $packageFullName "cabal.exe"
function Find-Entry {
param( [string] $app )
Get-Command -ErrorAction SilentlyContinue $app `
| Select-Object -first 1 `
| ForEach-Object { Split-Path $_.Path -Parent }
}
Function Execute-Command {
param( [string] $commandTitle
, [string] $commandPath
, [string] $commandArguments
)
Try {
$pinfo = New-Object System.Diagnostics.ProcessStartInfo
$pinfo.FileName = $commandPath
$pinfo.RedirectStandardError = $true
$pinfo.RedirectStandardOutput = $true
$pinfo.UseShellExecute = $false
$pinfo.Arguments = $commandArguments
$pinfo.WindowStyle = [Diagnostics.ProcessWindowStyle]::Hidden
$pinfo.CreateNoWindow = $true
$p = New-Object System.Diagnostics.Process
$p.StartInfo = $pinfo
$p.Start() | Out-Null
[pscustomobject]@{
commandTitle = $commandTitle
stdout = $p.StandardOutput.ReadToEnd()
stderr = $p.StandardError.ReadToEnd()
ExitCode = $p.ExitCode
}
$p.WaitForExit()
}
Catch {
exit
}
}
function Find-MSYS2 {
param()
# See if the user has msys2 already installed.
$msys2 = Find-Entry "msys2_shell.cmd"
if (($null -eq $msys2) -or ($msys2 -eq "")) {
$msys2 = Find-Entry "mingw*_shell.bat"
}
$dir_name = if ($is64) { 'msys64' } else { 'msys32' }
# Check for standalone msys2 installs
if (($null -eq $msys2) -or ($msys2 -eq "")) {
$tmp = Join-Path $Env:SystemDrive $dir_name
if (Test-Path $tmp -PathType Container) {
Write-Host "Standalone msys2 detected. Using default paths."
$msys2 = $tmp
}
}
if (($null -eq $msys2) -or ($msys2 -eq "")) {
# msys2 was not found already installed, assume user will install
# it in the default directory, so create the expected default msys2
# installation path.
$msys2 = "{0}\\{1}" -f (Get-ToolsLocation), $dir_name
}
Write-Debug "Msys2 directory: ${msys2}"
return $msys2
}
function ReadCabal-Config {
param( [string] $key )
$prog = "$cabal"
$cmd = "user-config diff -a ${key}:"
$proc = Execute-Command "Reading cabal config key '${key}'." $prog $cmd
if ($proc.ExitCode -ne 0) {
Write-Error $proc.stdout
Write-Error $proc.stderr
throw ("Could not read cabal configuration key '${key}'.")
}
$option = [System.StringSplitOptions]::RemoveEmptyEntries
$procout = $proc.stdout.Split([Environment]::NewLine) | Select-String "- ${key}" | Select-Object -First 1
if (!$procout) {
Write-Debug "No Cabal config for ${key}"
return {@()}.Invoke()
} else {
$value = $procout.ToString().Split(@(':'), 2, $option)[1].ToString()
$value = $value.Split([Environment]::NewLine)[0].Trim()
Write-Debug "Read Cabal config ${key}: ${value}"
return {$value.Replace('"','').Split(@(','), $option)}.Invoke()
}
}
function UpdateCabal-Config {
param( [string] $key
, [string[]] $values
)
if ((!$values) -or ($values.Count -eq 0)) {
$values = ""
} else {
#$value = '"' + [String]::Join("`",`"", $values) + '"'
$value = [String]::Join(",", $values)
}
$prog = "$cabal"
$cmd = "user-config update -a `"${key}: $value`""
$proc = Execute-Command "Update cabal config key '${key}'." $prog $cmd
if ($proc.ExitCode -ne 0) {
Write-Error $proc.stdout
Write-Error $proc.stderr
throw ("Could not update cabal configuration key '${key}'.")
}
Write-Debug "Wrote Cabal config ${key}: ${value}"
}
function Restore-Config-Cabal {
param()
$ErrorActionPreference = 'Stop'
$msys2_path = Find-MSYS2
$prog_path = ReadCabal-Config "extra-prog-path"
$lib_dirs = ReadCabal-Config "extra-lib-dirs"
$include_dirs = ReadCabal-Config "extra-include-dirs"
$native_path = if ($is64) { 'mingw64' } else { 'mingw32' }
$native_path = Join-Path $msys2_path $native_path
$msys_lib_dir = Join-Path $native_path "lib"
# Build new binary paths
$native_bin = Join-Path $native_path "bin"
$new_prog_paths = {$prog_path}.Invoke()
$new_prog_paths.Remove((Join-Path (Join-Path $msys2_path "usr") "bin")) | Out-Null
$new_prog_paths.Remove(($native_bin)) | Out-Null
$new_prog_paths = $new_prog_paths | Select-Object -Unique
# Build new library paths
$new_lib_dirs = {$lib_dirs}.Invoke()
$new_lib_dirs.Remove((Join-Path $native_path "lib")) | Out-Null
$new_lib_dirs = $new_lib_dirs | Select-Object -Unique
# Build new include paths
$new_include_dirs = {$include_dirs}.Invoke()
$new_include_dirs.Remove((Join-Path $native_path "include")) | Out-Null
$new_include_dirs = $new_include_dirs | Select-Object -Unique
UpdateCabal-Config "extra-prog-path" $new_prog_paths
UpdateCabal-Config "extra-lib-dirs" $new_lib_dirs
UpdateCabal-Config "extra-include-dirs" $new_include_dirs
Write-Host "Restored cabal configuration."
}
# Now execute cabal configuration updates
Restore-Config-Cabal
Uninstall-ChocolateyEnvironmentVariable -VariableName '_MSYS2_BASH'
Uninstall-ChocolateyEnvironmentVariable -VariableName '_MSYS2_PREFIX'
# Cleanup the batch file we created
Get-Command "mingw64-pkg.bat" -ErrorAction SilentlyContinue `
| ForEach-Object { Remove-Item -Force $_ -ErrorAction SilentlyContinue }
<#
.SYNOPSIS
Install a Mingw-w64 native package such that cabal and ghc will recognize them.
.DESCRIPTION
This CmdLet makes it easier to install native Mingw-w64 packages into MSYS2 such
that cabal-install and GHC can use them without any other configuration required.
This will not allow installation of MSYS2 packages. Your global namespace will
not be poluted by the use of this CmdLet.
.PARAMETER Action
The action to perform. Must be one of install, uninstall, update or shell.
- install: install a new native package
- uninstall: remove native package
- update: sync the repositories, will not upgrade any packages.
- shell: open a bash shell
.PARAMETER Package
The name of the Mingw64 package to install into the msys2 environment.
.PARAMETER NoConfirm
Indicates whether or not an interactive prompt should be used to confirm before
action is carried out.
.EXAMPLE
C:\PS> mingw-pkg install gtk2
.NOTES
Author: Tamar Christina
Date: February 16, 2019
#>
Param(
[ValidateSet("install","uninstall", "update", "shell")]
[String] $Action
, [string] $Package
, [string] $NoConfirm = "--confirm"
)
$bash = $Env:_MSYS2_BASH
$prefix = $Env:_MSYS2_PREFIX
if ((!$bash) -or ($bash -eq "") -or (!$prefix) -or ($prefix -eq "")) {
throw ("Bash environment variable found, are you sure you installed cabal and msys2 via chocolatey?")
}
if(![System.IO.File]::Exists($bash)){
throw ("Bash not found, try `choco install msys2' first.")
}
$package = "mingw-w64-${prefix}-${Package}"
$shell = $false
switch ($Action){
"install" {
$cmd = "-S"
if((!$Package) -or ($Package -eq "")){
throw ("Package name required when installing package.")
}
break
}
"uninstall" {
$cmd = "-R"
if((!$Package) -or ($Package -eq "")){
throw ("Package name required when removing package.")
}
break
}
"update" {
$cmd = "-Sy"
$package = ""
break
}
"shell" {
$shell = $true
break
}
default {
Write-Host ".SYNOPSIS
Install a Mingw-w64 native package such that cabal and ghc will recognize them.
.DESCRIPTION
This CmdLet makes it easier to install native Mingw-w64 packages into MSYS2 such
that cabal-install and GHC can use them without any other configuration required.
This will not allow installation of MSYS2 packages. Your global namespace will
not be poluted by the use of this CmdLet.
.PARAMETER Action
The action to perform. Must be one of install, uninstall, update or shell.
- install: install a new native package
- uninstall: remove native package
- update: sync the repositories, will not upgrade any packages.
- shell: open a bash shell
.PARAMETER Package
The name of the Mingw64 package to install into the msys2 environment.
.PARAMETER NoConfirm
Indicates whether or not an interactive prompt should be used to confirm before
action is carried out.
.EXAMPLE
C:\PS> mingw-pkg install gtk2 [--confirm|--noconfirm]
.NOTES
Author: Tamar Christina
Date: February 16, 2019"
return
}
}
switch ($NoConfirm){
"--noconfirm" {
$arg = "--noconfirm"
break
}
"--confirm" {
$arg = "--confirm"
break
}
default {
Write-Error "Unkown option $NoConfirm. Expected --confirm or --noconfirm."
return;
}
}
$osBitness = "64"
if ($prefix -eq "i686") {
$osBitness = "32"
}
# Set the APPDATA path which does not get inherited during these invokes
# and set MSYSTEM to make sure we're using the right system
$envdata = "export APPDATA=""" + $Env:AppData + """ && export MSYSTEM=MINGW" + $osBitness + " && "
if ($false -eq $shell) {
$proc = Start-Process -NoNewWindow -UseNewEnvironment -Wait $bash `
-ArgumentList '--login', '-c', "'$envdata pacman $cmd $arg $package'" `
-PassThru
if ((-not $ignoreExitCode) -and ($proc.ExitCode -ne 0)) {
throw ("`'${bash}`' did not complete successfully. ExitCode: " + $proc.ExitCode)
}
} else {
$proc = Start-Process -NoNewWindow -UseNewEnvironment -Wait $bash `
-ArgumentList '--login' `
-PassThru
}
No results available for this package. We are building up results for older packages over time so expect to see results. If this is a new package, it should have results within a day or two.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
Cabal 3.10.3.0 | 10 | Wednesday, July 17, 2024 |
Waiting for Maintainer
|
|
Cabal 3.10.2.0 | 48456 | Saturday, November 18, 2023 | Approved | |
Cabal 3.10.1.1 | 56153 | Thursday, March 23, 2023 | Approved | |
Cabal 3.8.1.0 | 136241 | Tuesday, August 9, 2022 | Approved | |
Cabal 3.6.2.0 | 161312 | Wednesday, October 13, 2021 | Approved | |
Cabal 3.6.0.0 | 784 | Wednesday, October 13, 2021 | Approved | |
Cabal 3.4.1.0 | 7526 | Wednesday, October 13, 2021 | Approved | |
Cabal 3.4.0.1-rc3 | 5146 | Thursday, December 24, 2020 | Approved | |
Cabal 3.4.0.0 | 100116 | Friday, February 26, 2021 | Approved | |
Cabal 3.4.0.0-rc5 | 2686 | Sunday, January 3, 2021 | Exempted | |
Cabal 3.4.0.0-rc3 | 330 | Saturday, October 10, 2020 | Exempted | |
Cabal 3.2.0.0 | 112511 | Friday, April 10, 2020 | Approved | |
Cabal 3.0.0.0 | 31345 | Thursday, August 29, 2019 | Approved | |
Cabal 2.4.1.0 | 28778 | Monday, November 26, 2018 | Approved | |
Cabal 2.4.0.20180922 | 2569 | Sunday, September 23, 2018 | Approved | |
Cabal 2.4.0.0 | 1561 | Saturday, September 22, 2018 | Approved | |
Cabal 2.2.0.0 | 6403 | Thursday, March 29, 2018 | Approved | |
Cabal 2.0.0.1 | 2792 | Tuesday, February 6, 2018 | Approved | |
Cabal 2.0.0.0 | 5723 | Thursday, August 17, 2017 | Approved | |
Cabal 1.24.0.2 | 4666 | Saturday, January 14, 2017 | Approved | |
Cabal 1.24.0.0 | 5052 | Saturday, May 14, 2016 | Approved | |
Cabal 1.22.0.0 | 419 | Saturday, May 14, 2016 | Approved | |
Cabal 1.20.0.3 | 466 | Tuesday, May 17, 2016 | Approved | |
Cabal 1.20.0.2 | 470 | Saturday, May 14, 2016 | Approved | |
Cabal 1.20.0.1 | 442 | Saturday, May 14, 2016 | Approved | |
Cabal 1.18.0.3 | 438 | Saturday, May 14, 2016 | Approved | |
Cabal 1.18.0.2 | 415 | Saturday, May 14, 2016 | Approved | |
Cabal 1.18.0.1 | 458 | Saturday, May 14, 2016 | Approved | |
Cabal 0.14.0 | 436 | Saturday, May 14, 2016 | Approved | |
Cabal 0.10.2 | 420 | Saturday, May 14, 2016 | Approved | |
Cabal 0.8.2 | 477 | Saturday, May 14, 2016 | Approved | |
Cabal 0.8.0 | 432 | Saturday, May 14, 2016 | Approved | |
Cabal 0.6.4 | 435 | Saturday, May 14, 2016 | Approved | |
Cabal 0.6.2 | 478 | Saturday, May 14, 2016 | Approved | |
Cabal 0.6.0 | 485 | Saturday, May 14, 2016 | Approved |
Copyright (c) 2003-2023, Isaac Jones, Simon Marlow, Martin Sjögren, Bjorn Bringert, Krasimir Angelov, Malcolm Wallace, Ross Patterson, Lemmih, Paolo Martini, Don Stewart, Duncan Coutts
This package has no dependencies.
Ground Rules:
- This discussion is only about Cabal and the Cabal 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 Cabal, 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.
Phyx (maintainer) on 12 Jun 2024 19:16:27 +00:00:
User 'Phyx' (maintainer) submitted package.
chocolatey-ops (reviewer) on 12 Jun 2024 19:51:37 +00:00:
cabal has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
chocolatey-ops (reviewer) on 12 Jun 2024 23:06:42 +00:00:
cabal has failed automated package testing (verification).
Please visit https://gist.github.com/choco-bot/0a4fad0ba3c6b1a56b736d5c378fa5fc for details.
The package status will be changed and will be waiting on your next actions.
Phyx (maintainer) on 13 Jun 2024 03:28:02 +00:00:
User 'Phyx' (maintainer) submitted package.
chocolatey-ops (reviewer) on 13 Jun 2024 04:03:38 +00:00:
cabal has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
Phyx (maintainer) on 13 Jun 2024 04:31:52 +00:00:
Rerun
Validation Status Change - Validation tests have been set to rerun.
chocolatey-ops (reviewer) on 13 Jun 2024 04:33:44 +00:00:
cabal has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
chocolatey-ops (reviewer) on 13 Jun 2024 05:44:53 +00:00:
cabal has failed automated package testing (verification).
Please visit https://gist.github.com/choco-bot/88c16ed135fd40207948747aa02cf843 for details.
The package status will be changed and will be waiting on your next actions.
Phyx (maintainer) on 14 Jun 2024 04:20:33 +00:00:
User 'Phyx' (maintainer) submitted package.
chocolatey-ops (reviewer) on 14 Jun 2024 04:56:14 +00:00:
cabal has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
chocolatey-ops (reviewer) on 14 Jun 2024 05:05:23 +00:00:
cabal has failed automated package testing (verification).
Please visit https://gist.github.com/choco-bot/64c2687c678619abbdf5710bf4aa2c6f for details.
The package status will be changed and will be waiting on your next actions.
Phyx (maintainer) on 15 Jun 2024 06:18:55 +00:00:
the error is odd, package not found? works fine locally
Verification Status Change - Verification tests have been set to rerun.
chocolatey-ops (reviewer) on 15 Jun 2024 06:20:34 +00:00:
cabal has failed automated package testing (verification).
Please visit https://gist.github.com/choco-bot/9ca077e6ff5a05f68f9fe8cf7a55ec59 for details.
The package status will be changed and will be waiting on your next actions.
chocolatey-ops (reviewer) on 04 Jul 2024 04:58:55 +00:00:
We've found cabal v3.10.3.0 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.
Take action:
If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.
Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.
Phyx (maintainer) on 17 Jul 2024 20:52:56 +00:00:
User 'Phyx' (maintainer) submitted package.
chocolatey-ops (reviewer) on 17 Jul 2024 21:24:43 +00:00:
cabal has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
chocolatey-ops (reviewer) on 17 Jul 2024 21:38:59 +00:00:
cabal has failed automated package testing (verification).
Please visit https://gist.github.com/choco-bot/8a8ce718fc652d6e5efb144024f21006 for details.
The package status will be changed and will be waiting on your next actions.