Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document ways to declare sources and patches #3405

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Document ways to declare sources and patches #3405

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 20 additions & 1 deletion docs/manual/spec.md
View file
Open in desktop
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
Loading