Downloads:

25,130

Downloads of v 0.0.1:

25,130

Last Update:

31 Aug 2019

Package Maintainer(s):

Software Author(s):

  • Tamar Christina

Tags:

cabal ghc haskell

Haskell Development Environment

0.0.1 | Updated: 31 Aug 2019

Downloads:

25,130

Downloads of v 0.0.1:

25,130

Maintainer(s):

Software Author(s):

  • Tamar Christina

Tags:

cabal ghc haskell

Haskell Development Environment 0.0.1

Some Checks Have Failed or Are Not Yet Complete

1 Test Passing and 1 Failing Test


Validation Testing Passed


Verification Testing Failed

Details

To install Haskell Development Environment, run the following command from the command line or from PowerShell:

>

To upgrade Haskell Development Environment, run the following command from the command line or from PowerShell:

>

To uninstall Haskell Development Environment, run the following command from the command line or from PowerShell:

>

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

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

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

3. Enter your internal repository url

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

4. Choose your deployment method:


choco upgrade haskell-dev -y --source="'STEP 3 URL'" [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 haskell-dev -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Ensure haskell-dev installed
  win_chocolatey:
    name: haskell-dev
    state: present
    version: 0.0.1
    source: STEP 3 URL

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

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'haskell-dev' do
  action    :install
  version  '0.0.1'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: haskell-dev,
    Version: 0.0.1,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller haskell-dev
{
   Name     = 'haskell-dev'
   Ensure   = 'Present'
   Version  = '0.0.1'
   Source   = 'STEP 3 URL'
}

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


package { 'haskell-dev':
  provider => 'chocolatey',
  ensure   => '0.0.1',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install haskell-dev version="0.0.1" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator Pauby on 26 Nov 2019.

Description

This is an opinionated automated environment for performing Haskell development on windows
using GHC and Cabal along with MSYS2. The goal of the project is to create as minimal of
indirections between you and the tools as possible in order to simplify things and make
things easier to understand and debug. The core premise of the project is to integrate into
Windows and not box off or isolate Haskell tools from other tools while using no or as few
global state as possible.

This package will automatically configure msys2 for use by cabal. If you already have msys2
install then nothing else needs to be done. Otherwise msys2 will be installed for you.

Lastly in order to facilitate package installations a new CmdLet mingw64-pkg is created to make it easier to install
native dependencies such as gtk.

C:\PS> mingw-pkg install gtk2

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.

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

An optional last parameter can be used to force a prompt before installing a package.
Default is off.

C:\PS> mingw-pkg install gtk2 $true

For AppVeyor use we recommend installing the ghc and cabal packages directly as to not install msys2 twice.
You will still have access to mingw-pkg.


LICENSE.txt
The MIT License (MIT)

Copyright (c) 2019 Tamar Christina

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

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.

Version Downloads Last Updated Status

Discussion for the Haskell Development Environment Package

Ground Rules:

  • This discussion is only about Haskell Development Environment and the Haskell Development Environment 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 Haskell Development Environment, 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