From 71ce0d6cc440eec89fcd11b24a9bbce77b22d5f5 Mon Sep 17 00:00:00 2001 From: Otto Liljalaakso Date: Sun, 27 Oct 2024 22:46:43 +0200 Subject: [PATCH] Document ways to declare sources and patches --- docs/manual/spec.md | 21 ++++++++++++++++++++- 1 file changed, 20 insertions(+), 1 deletion(-) diff --git a/docs/manual/spec.md b/docs/manual/spec.md index 8be520c46c..ca1705d64c 100644 --- a/docs/manual/spec.md +++ b/docs/manual/spec.md @@ -177,10 +177,17 @@ Arbitrary number of sources may be declared, for example: Source1: mysoft-data-1.0.zip ``` +Source numbers do not need to be consecutive and may include leading zeroes. +Unnumbered source tag `Source:` is also supported and is automatically assigned +the next available integer. + #### Patch Used to declare patches applied on top of sources. All patches declared -will be packaged into source rpms. +will be packaged into source rpms. Just like sources, patches can be +numbered or unnumbered and are indexed the same way. Unless there is a +specific reason to use numbered patches, the recommended approach is to use +unnumbered patches and apply them using `%autosetup` or `%autopatch`. #### Icon @@ -472,6 +479,18 @@ software). ### Sub-sections +#### `%sourcelist` + +List of sources, one per line. Handled like unnumbered Source tags. For +clarity, mixing Source tags and `%sourcelist` in one specfile is not +recommended. + +#### `%patchlist` + +List of patches, one per line. Handled like unnumbered Patch tags. For +clarity, mixing Patch tags and `%patchlist` in one specfile is not +recommended. + #### `%package [-n]` `%package ` starts a preamble section for a new sub-package.