Skip to content

Commit

Permalink
Document ways to declare sources and patches
Browse files Browse the repository at this point in the history
  • Loading branch information
oturpe committed Jan 1, 2025
1 parent 4d621e4 commit 71ce0d6
Showing 1 changed file with 20 additions and 1 deletion.
21 changes: 20 additions & 1 deletion docs/manual/spec.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -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]<name>`

`%package <name>` starts a preamble section for a new sub-package.
Expand Down

0 comments on commit 71ce0d6

Please sign in to comment.