[Rpm-maint] [rpm-software-management/rpm] `%patchlist` should have a way to group patches (Issue #3109)

[Bernhard Rosenkraenzer]

In a few contexts, it is necessary to make a difference between a few groups of patches that have to be applied at a different time, under different conditions, or in a different subdirectory.
Using the traditional `Patch1234:` tags, this is possible with `%autopatch -m ...` / `%autopatch -M`, e.g.

```
Patch0: https://github.com/upstream-project/pull/1234.patch
Patch1: https://github.com/upstream-project/pull/1235.patch
Patch100: https://github.com/other-project/pull/5678.patch
Patch101: https://github.com/other-project/pull/5679.patch
[...]
%autopatch -M 99
cd evil-internalized-copies-of-3rd-party-libs/other-project
%autopatch -m 100
```

(And yes, the correct fix for this is to not use the bundled copy - but it's not always possible, e.g. if the internalized version is modified)

With `%patchlist`, there is currently no way [at least none that I'm aware of, if it exists, it needs to be documented] to mark which patches should belong to which group. It would be nice to be able to do something like

```
%patchlist
https://github.com/upstream-project/pull/1234.patch
https://github.com/upstream-project/pull/1235.patch
100:https://github.com/other-project/pull/5678.patch
https://github.com/other-project/pull/5679.patch
```

where the added `100:` for the first patch from `other-project` would increment the internal counter to 100, so
`1234.patch` would be `0`, `1235.patch` would be 1, `5678.patch` would be `100` and `5679.patch` would be `101`.


-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/3109
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/issues/3109 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20240517/89a8fed2/attachment-0001.html>