aboutsummaryrefslogtreecommitdiff
path: root/pkgs/development/compilers/purescript/psc-package (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Recover the complicated situation after my bad mergeVladimír Čunát2020-10-261-6/+4
| | | | | | | | | | | | | | | | | I made a mistake merge. Reverting it in c778945806b undid the state on master, but now I realize it crippled the git merge mechanism. As the merge contained a mix of commits from `master..staging-next` and other commits from `staging-next..staging`, it got the `staging-next` branch into a state that was difficult to recover. I reconstructed the "desired" state of staging-next tree by: - checking out the last commit of the problematic range: 4effe769e2b - `git rebase -i --preserve-merges a8a018ddc0` - dropping the mistaken merge commit and its revert from that range (while keeping reapplication from 4effe769e2) - merging the last unaffected staging-next commit (803ca85c209) - fortunately no other commits have been pushed to staging-next yet - applying a diff on staging-next to get it into that state
* Revert "Merge #101508: libraw: 0.20.0 -> 0.20.2"Vladimír Čunát2020-10-251-4/+6
| | | | | | | I'm sorry; I didn't notice it contained staging commits. This reverts commit 17f5305b6c20df795c365368d2d868266519599e, reversing changes made to a8a018ddc0a8b5c3d4fa94c94b672c37356bc075.
* psc-package: Adopt new installShellCompletion syntaxLily Ballard2020-10-081-6/+4
|
* psc-package: Stop using haskellPackages to buildLily Ballard2020-03-191-18/+52
| | | | | | | | | | Switch to the approach taken by https://github.com/justinwoo/easy-purescript-nix/blob/master/psc-package-simple.nix This downloads a prebuilt release and patches the linker paths. It reduces the number of supported platforms, but ensures we're using the official supported psc-package compiler. The `haskellPackages` approach wasn't supported and was leading to version conflicts with dependencies.
* psc-package: 0.6.0 -> 0.6.2R. RyanTM2020-02-111-2/+2
|
* psc-package: 0.5.1 -> 0.6.0R. RyanTM2020-01-261-2/+2
|
* psc-package: 0.4.2 -> 0.5.1R. RyanTM2019-01-311-2/+2
| | | | | | | Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/psc-package/versions
* psc-package: 0.4.1 -> 0.4.2R. RyanTM2018-11-091-2/+2
| | | | | | | Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/psc-package/versions
* psc-package: 0.3.2 -> 0.4.1Justin Woo2018-07-281-4/+5
| | | | | | | | | Updates that remove features and improve user experience. Adds warnings for trying to install packages without (purescript/psc-package#126 by @Dretch) Filters "installing" messages for build (purescript/psc-package#130 by @Dretch) Adds options for limiting jobs for install (purescript/psc-package#127 by @vladciobanu) Per purescript/psc-package#121, removes the confusing misfeature "add-from-bower", which led to many users thinking this command was for adding "extra-deps" like Stack. See the thread for details on how you could readily replace this command if you used it before.
* psc-package v0.3.2-pre -> v0.3.2Jonathan Curran2018-04-071-2/+2
| | | | v0.3.2 is released
* psc-package: 0.2.5 -> 0.3.2-preMaxime Dénès2018-03-311-2/+2
| | | | | Note: the previous version was not building due to outdated upstream dependencies.
* maintainers: capitalize the Profpatsch attribute (vanity)Profpatsch2018-02-121-1/+1
| | | | Since I’m already at it, this has been bothering me for a while.
* psc-package: 0.2.4 -> 0.2.5Tomasz Rybarczyk2017-12-041-2/+2
|
* psc-package: 0.2.0 -> 0.2.4Maxime Dénès2017-11-081-2/+2
|
* psc-package: 0.1.1 -> 0.2.0Profpatsch2017-07-121-2/+2
|
* psc-package: init at 0.1.1Profpatsch2017-04-151-0/+26
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-01 06:13:14 +0000