From 370c72d9bf9c95e59d3636d17cae7afbe35542a8 Mon Sep 17 00:00:00 2001 From: Davide Cavalca Date: Apr 13 2022 15:46:24 +0000 Subject: Correct spin release package name and clarify its usage --- diff --git a/docs/spin.md b/docs/spin.md index ffae21f..fbf60d8 100644 --- a/docs/spin.md +++ b/docs/spin.md @@ -4,12 +4,12 @@ CentOS SIGs can create spins of the distribution if they so desire. A spin in th ## Making a spin To create a new spin, you will need a few dedicated packages to properly identify the spin: -- add a `centos-spin-$name-release` subpackage to your SIG release package ([example](https://git.centos.org/rpms/centos-release-hyperscale/blob/c8s-sig-hyperscale/f/SPECS/centos-release-hyperscale.spec)) +- add a `centos-release-$name-spin` subpackage to your SIG release package ([example](https://git.centos.org/rpms/centos-release-hyperscale/blob/c8s-sig-hyperscale/f/SPECS/centos-release-hyperscale.spec)); this subpackage should either require or include any repository definitions that are needed for the spin to work - branch [`centos-stream-release`](`https://git.centos.org/rpms/centos-stream-release) and add a `centos-stream-spin-$name-release` subpackage to it; make sure to set `VARIANT` and `VARIANT_ID` in [os-release](https://www.freedesktop.org/software/systemd/man/os-release.htmll#VARIANT=) to properly identify the spin and to add a `Requires` for the spin release package ([example](https://git.centos.org/rpms/centos-stream-release/blob/c8s-sig-hyperscale-spin/f/SPECS/centos-stream-hyperscale-spin-release.spec)) Within these packages, `$name` should either be the name of the SIG (if producing only one spin), or the name of the SIG followed by the name of the spin. -We recommend using a dedicated destination tag in CBS for spin-specific packages. This is especially important if the spin includes packages that will only work properly within the spin itself (i.e. they are not suitable for installation on stock CentOS systems). +We recommend using a dedicated destination tag in CBS for spin-specific packages, and including the corresponding repository definition in your `centos-release-$name-spin` subpackage. This is especially important if the spin includes packages that will only work properly within the spin itself (i.e. they are not suitable for installation on stock CentOS systems). Spins produced by a SIG should be documented on its wiki page as deliverables.