-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rename package to spago-legacy
to help NixPkgs
#3
Conversation
710089e
to
30d0eb4
Compare
This package is currently `spago` in NixPkgs: https://search.nixos.org/packages?channel=unstable&from=0&size=50&sort=relevance&type=packages&query=spago The Nix configuration for that is generated from this Cabal file. Renaming to `spago-legacy` will help NixPkgs update to the new Spago. I think it's unnecessary for the `spago` binary to be renamed.
30d0eb4
to
02f95a4
Compare
We don't have release CI set up on this repo, so it might take more work to build the binaries. Will nixpkgs need the binaries or will it build them off the branch? In other words: will just cutting the release tag enough for nixpkgs? |
NixPkgs will not need the binaries. From what I can understand about this script Thanks |
Thanks, that makes sense. I can merge this PR and cut a new tag, but we'll need to get CI going first - the |
I can disable the unnecessary jobs in |
0ec9654
to
f7a04f9
Compare
I don't think the Mac build is necessary to support the Darwin platform of the Nix build:
It is going to build Spago directly from source, given the release package. |
81dfb13
to
df95f0d
Compare
@@ -39,7 +39,7 @@ jobs: | |||
- uses: actions/checkout@v2 | |||
- name: Setup Haskell (macOS and Windows) | |||
if: runner.os != 'Linux' | |||
uses: haskell/actions/setup@v1 | |||
uses: haskell-actions/setup@v2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
df95f0d
to
b3a5ecc
Compare
b3a5ecc
to
de6d5ce
Compare
@f-f please review again |
@f-f please review again |
I merged and cut the new release. Please keep me posted on the progress in nixpkgs!
Let's do the renaming, it's quite confusing to have the two things share the same binary name. |
The Spago package in NixPkgs has moved from https://github.com/purescript/spago to https://github.com/purescript/spago-legacy. I believe the new `spago` https://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 from `spago` to `spago-legacy`. Because part of this is generated by `cabal2nix`, changes to the `spago-legacy` Cabal file are needed: purescript/spago-legacy#3
Thanks @f-f , here is the WIP NixOS/nixpkgs#324944 I will rename the binary to |
Description of the change
This package is currently
spago
in NixPkgs:https://search.nixos.org/packages?channel=unstable&from=0&size=50&sort=relevance&type=packages&query=spago
The Nix configuration for that is generated from this Cabal file. Renaming to
spago-legacy
will help clear the path for NixPkgs update to the new Spago.I think it's unnecessary for the
spago
binary to be renamed tospago-legacy
.If this PR is merged, NixPkgs will be updated to the latest commit in this repo
spago-legacy
.succeeds with GHC 9.2
stack build
succeeds.Please merge this PR and make a fix version/release 0.21.1 or maybe even 0.21.0.1. This is probably necessary for Nix to grab the latest commit, I don't think it works directly off the branch.
Checklist:
README
P.S.: the above checks are not compulsory to get a change merged, so you may skip them. However, taking care of them will result in less work for the maintainers and will be much appreciated 😊