spago-legacy: 0.21.0 -> 0.21.1, rename from spago#324944
spago-legacy: 0.21.0 -> 0.21.1, rename from spago#324944sternenseemann merged 3 commits intoNixOS:staging-nextfrom
Conversation
pkgs/development/tools/purescript/spago-legacy/spago-legacy.nix
Outdated
Show resolved
Hide resolved
9860009 to
b10e5fa
Compare
|
Hi, what's the state of this? spago with fsnotify >= 4 would be great for #429810! |
b10e5fa to
d41a74d
Compare
|
@peterbecich I went ahead and updated this to update to spago-legacy 0.21.1. Thanks for all your work on this! |
spago-legacy|
|
Tests are resolved by applying Gabriella439/turtle#459 on |
d41a74d to
cca43b5
Compare
This comment was marked as outdated.
This comment was marked as outdated.
cca43b5 to
9abf641
Compare
pkgs/top-level/aliases.nix
Outdated
| @@ -2340,6 +2340,7 @@ mapAliases { | |||
| soundOfSorting = sound-of-sorting; # Added 2023-07-07 | |||
| SP800-90B_EntropyAssessment = sp800-90b-entropyassessment; # Added on 2024-06-12 | |||
| SPAdes = spades; # Added 2024-06-12 | |||
| spago = spago-legacy; # Added 2025-09-23 | |||
There was a problem hiding this comment.
Is this supposed to stay forever, or be removed eventually?
If the latter, we should add a warning based on lib.warnOnInstantiate. If the former, we should add a reason why it needs to stay.
There was a problem hiding this comment.
It really depends. Ideally, we'd just package “spago@next” at pkgs.spago which would upgrade it seamlessly for existing users. I do not know when/if this is going to happen. I will not invest time into this as I don't use PureScript. My impression is that purescript doesn't receive a lot of attention in Nixpkgs lately, but I may be wrong.
Upstream PureScript devs seem to have little interest in having their work packaged by Nixpkgs and provide an overlay instead.
There was a problem hiding this comment.
chiming in as the main Spago maintainer - spago-legacy is not likely to see any maintenance, so once spago-next is stable for some amount of time and we feel like we have migrated the majority of the community then we can properly deprecate it. But yes, as @sternenseemann mentioned usually people that are looking for purescript tooling in nix will use our overlay.
See purescript/spago-legacy#3. Co-authored-by: Peter Becich <[email protected]>
a769f07 to
a404f73
Compare
|
The Spago package in NixPkgs has moved from
https://github.com/purescript/spago to https://github.com/purescript/spago-legacy.
I believe the new
spagohttps://github.com/purescript/spago is a rewrite from Haskell to PureScript. To support this new Spago in NixPkgs will probably require rewriting all of the Nix configuration. I.m.o. the easiest way to clear the path for this is to rename the old Nix configuration fromspagotospago-legacy.Because part of this is generated byThis has been done now.cabal2nix, changes to thespago-legacyCabal file are needed: purescript/spago-legacy#3Description of changes
Things done
nix.conf? (See Nix manual)sandbox = relaxedsandbox = truenix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)Add a 👍 reaction to pull requests you find important.