(cherry picked from commit f3de8a3c)

Matthew Pickering authored 2 years ago and Ben Gamari committed 1 year ago

This is dynamically linked and makes creating statically linked
executables more straightforward.

Fixes #23482

(cherry picked from commit 51b57d65)

Matthew Pickering authored 1 year ago and Ben Gamari committed 1 year ago

This adds builds for the latest releases for fedora and debian

We build these bindists in nightly and release pipelines.

(cherry picked from commit 8f7d3041)

Matthew Pickering authored 1 year ago and Ben Gamari committed 1 year ago

deb9 is now EOL so it's time to upgrade the i386 bindist to use deb10

Fixes #23585

(cherry picked from commit c39f279b)

Matthew Pickering authored 2 years ago and Marge Bot committed 2 years ago

We currently attempt to build and distribute fully static alpine
bindists (ones which could be used on any linux platform) but most
people who use the alpine bindists want to use alpine to build their own
static applications (for which a fully static bindist is not necessary).
We should build and distribute these bindists for these users whilst the
fully-static bindist is still unusable.

Fixes #23349

Matthew Pickering authored 2 years ago and Marge Bot committed 2 years ago

These were not uploaded for alpha1

Fixes #22844

Matthew Pickering authored 2 years ago and Marge Bot committed 2 years ago

This check makes sure that if a job is a prefixed by "release-" then the
script downloads it and understands how to map the job name to the
platform.

Matthew Pickering authored 2 years ago and Marge Bot committed 2 years ago

We intend to release rocky8 bindist so the fetching script needs to know
about them.

Matthew Pickering authored 2 years ago and Marge Bot committed 2 years ago

This adds release jobs for ubuntu18_04 which uses glibc 2.27 which is
older than the 2.28 which is used by Rocky8 bindists.

Ticket #22268

Matthew Pickering authored 2 years ago and Marge Bot committed 2 years ago

It is better to keep these scripts in the tree as they depend on the CI
configuration and so on. By keeping them in tree we can keep them
up-to-date as the CI config changes and also makes it easier to backport
changes to the release script between release branches in future.

The final motivation is that it makes generating GHCUp metadata
possible.