Skip to content

Commit

Permalink
releng/tag-release.sh: no longer ship zbm-kcl as a release asset
Browse files Browse the repository at this point in the history
  • Loading branch information
zdykstra committed Feb 11, 2024
1 parent 0a0d47d commit f8f6597
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 15 deletions.
15 changes: 8 additions & 7 deletions docs/general/binary-releases.rst
Original file line number Diff line number Diff line change
@@ -1,13 +1,14 @@
Binary Releases
===============

ZFSBootMenu releases include pre-built ``release`` and ``recovery`` images, each distributed as an EFI executable or a
"component" archive consisting of a separate kernel and initramfs image. The EFI executables should be directly bootable
by most UEFI firmware implementations or boot managers including rEFInd, gummiboot and systemd-boot. The separate kernel
and initramfs components may also be used on UEFI systems; the kernels used for ZFSBootMenu binary releases always
include the built-in EFI stub and may be directly bootable (provided the UEFI implementation can pass command-line
arguments, including the path to the associated initramfs image, to the kernel) or loaded by a boot manager. In
addition, the separate components may be booted by any standard BIOS boot loader (*e.g.*, syslinux) on legacy hardware.
ZFSBootMenu releases include `pre-built <https://get.zfsbootmenu.org/>`_ ``release`` and ``recovery`` images, each
distributed as an EFI executable or a "component" archive consisting of a separate kernel and initramfs image. The EFI
executables should be directly bootable by most UEFI firmware implementations or boot managers including rEFInd,
gummiboot and systemd-boot. The separate kernel and initramfs components may also be used on UEFI systems; the kernels
used for ZFSBootMenu binary releases always include the built-in EFI stub and may be directly bootable (provided the
UEFI implementation can pass command-line arguments, including the path to the associated initramfs image, to the
kernel) or loaded by a boot manager. In addition, the separate components may be booted by any standard BIOS boot loader
(*e.g.*, syslinux) on legacy hardware.

Release images
~~~~~~~~~~~~~~
Expand Down
8 changes: 0 additions & 8 deletions releng/tag-release.sh
Original file line number Diff line number Diff line change
Expand Up @@ -147,14 +147,6 @@ if ! releng/make-binary.sh "${release}"; then
error "ERROR: unable to make release assets, exiting!"
fi

# Copy in any extra assets/files, relative to the project root
# shellcheck disable=SC2043
for extra in bin/zbm-kcl ; do
[ -f "${extra}" ] || error "ERROR: missing ${extra}"
cp "${extra}" "${asset_dir}/"
assets+=( "${extra##*/}" )
done

# Sign the binary assets
if ! releng/sign-assets.sh "${release}"; then
error "ERROR: unable to sign release assets, exiting!"
Expand Down

0 comments on commit f8f6597

Please sign in to comment.