Downloads:

4,281

Downloads of v 0.7.3:

345

Last Update:

17 Aug 2015

Package Maintainer(s):

Software Author(s):

  • Phil Freeman
  • Gary Burgess
  • and other contributors

Tags:

programming purescript javascript compile Haskell

PureScript

This is not the latest version of PureScript available.

  • 1
  • 2
  • 3

0.7.3 | Updated: 17 Aug 2015

Downloads:

4,281

Downloads of v 0.7.3:

345

Software Author(s):

  • Phil Freeman
  • Gary Burgess
  • and other contributors

  • 1
  • 2
  • 3
PureScript 0.7.3

This is not the latest version of PureScript available.

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details

To install PureScript, run the following command from the command line or from PowerShell:

>

To upgrade PureScript, run the following command from the command line or from PowerShell:

>

To uninstall PureScript, 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://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

3. Enter your internal repository url

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

4. Choose your deployment method:


choco upgrade purescript -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 purescript -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 purescript installed
  win_chocolatey:
    name: purescript
    state: present
    version: 0.7.3
    source: STEP 3 URL

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


chocolatey_package 'purescript' do
  action    :install
  version  '0.7.3'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: purescript,
    Version: 0.7.3,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller purescript
{
   Name     = 'purescript'
   Ensure   = 'Present'
   Version  = '0.7.3'
   Source   = 'STEP 3 URL'
}

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


package { 'purescript':
  provider => 'chocolatey',
  ensure   => '0.7.3',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install purescript version="0.7.3" 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 ferventcoder on 28 Dec 2015.

Description

A small strongly, statically typed language that compiles to Javascript. This package is 64-bit only, and uses the files from the official release.


tools\bin\psc-bundle.exe
md5: E6D8C4D118194ACC85A53643807C39BB | sha1: 7472ADC050A58E475E45C651E17004FBD2716166
tools\bin\psc-docs.exe
md5: 48D7C7372E62B65AE3914E4D737196A8 | sha1: 7A6AD8D20DA0B7E3B151EFB9080B425ED5212CE2
tools\bin\psc-publish.exe
md5: CADE6D95749C89E50A4C6755A4614DDC | sha1: A8244F9FCCBF8F8F3EB0E4FA209F9B408445FE3C
tools\bin\psc.exe
md5: BFDF7E0F4D01E5E922738905D7EAABE4 | sha1: 9F78E8DE943CC934BED44D7CA3C08CDDB371AF26
tools\bin\psci.exe
md5: 7CE761346AE3E17538D79A04C34BCD45 | sha1: 44AABD6331F4E9481A5CE1AE19F0151CAE7FBBC3
tools\INSTALL.md
# Installation information

If you are having difficulty installing the PureScript compiler, feel free to
ask for help! A good place is the #purescript IRC channel on Freenode, or
alternatively Stack Overflow.

## Using prebuilt binaries

The prebuilt binaries are compiled with GHC 7.8.3, and therefore they should
run on any operating system supported by GHC 7.8.3, such as:

* Windows 2000 or later,
* OS X 10.7 or later,
* Linux ??? (we're not sure what the minimum version is).

This list is not exhaustive. If your OS is too old or not listed, or if the
binaries fail to run, you may be able to install the compiler by building it
from source; see below.

It's probably safe to assume that other prebuilt distributions (eg, Homebrew,
Chocolatey, AUR, npm) use the same binaries, and therefore have the same
requirements.

## Compiling from source

GHC 7.6.1 or newer is required to compile from source. The easiest way is to
use `cabal-install`:

```
$ cabal update && cabal install purescript
```

The PureScript compiler has been known to run on OS X 10.6 when built with GHC
7.6.

## The "curses" library

`psci` depends on the `curses` library (via the Haskell package `terminfo`). If
you are having difficulty running the compiler, it may be because the `curses`
library is missing.

On Linux, you will probably need to install `ncurses` manually. On Ubuntu, for
example, this can be done by running:

```
$ sudo apt-get install libncurses5-dev
```
tools\LICENSE
 
tools\README
 

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
purescript 0.14.2 34 Monday, June 14, 2021 Approved
purescript 0.14.1 44 Tuesday, April 20, 2021 Approved
purescript 0.14.0 46 Monday, March 1, 2021 Approved
purescript 0.13.8 197 Wednesday, May 27, 2020 Approved
purescript 0.13.6 314 Monday, January 20, 2020 Approved
purescript 0.13.5 109 Thursday, November 14, 2019 Approved
purescript 0.13.4 106 Monday, October 21, 2019 Approved
purescript 0.13.3 98 Monday, August 19, 2019 Approved
purescript 0.12.5 275 Monday, April 15, 2019 Approved

This package has no dependencies.

Discussion for the PureScript Package

Ground Rules:

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