-
Notifications
You must be signed in to change notification settings - Fork 842
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
Updates for -static
Stack bindist suffix
#5288
Comments
snoyberg
added a commit
that referenced
this issue
Jun 21, 2020
snoyberg
added a commit
that referenced
this issue
Jun 28, 2020
snoyberg
added a commit
that referenced
this issue
Sep 21, 2020
snoyberg
added a commit
that referenced
this issue
Sep 21, 2020
snoyberg
added a commit
that referenced
this issue
Jun 1, 2021
Implements points (2) and (3) from issue #5288.
snoyberg
added a commit
that referenced
this issue
Jun 1, 2021
This implements the final piece of and closes out #5288
borsboom
pushed a commit
that referenced
this issue
Jun 2, 2021
Implements points (2) and (3) from issue #5288.
borsboom
pushed a commit
that referenced
this issue
Jun 2, 2021
This implements the final piece of and closes out #5288
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Update CI build to produce a
linux-x86_64-static
bindist. It should be the same as thelinux-x86_64
version (which is now also static) but the directory name must uselinux-x86_64-static
sincestack upgrade
requires the directory name to match the bindist name.Modify
stack upgrade
to download bindists fromhttps://get.haskellstack.org/upgrade/
(e.g. https://get.haskellstack.org/upgrade/linux-x86_64.tar.gz) instead of directly from the Github release, to make it more future proof.Modify
stack upgrade
so that it doesn't require the downloaded tarball's top-level path component to match the name of the tarball. Just strip off the top-level path component (like to tar's--strip-components 1
). This will allow us to set up redirects from get.haskellstack.org/upgrade in the future.The text was updated successfully, but these errors were encountered: