@kloczek I am fully aware of the autonumbering functionality for
sources/patches, but SourceCSum is not backward compatible with older rpm
versions, so you would have to do something like
```spec
%if %{with somecondition}
Source: file1
%if %rpm_is_new_enough
SourceCSum: sha256(checksum)
%endif
%else
Source: file1
%if %rpm_is_new_enough
SourceCSum: sha256(checksum)
%endif
%endif
```
I feel like this looks super ugly. in suse spec files all conditionalized
statements are ordered near the end, so there could be dozens to hundreds of
lines between the first block and the second block. it is very confusing.
having it in one line avoids all of that.
Regarding the `<csum_alg>` and also using something like `github:/` you can
totally do both in both my suggestions as well, so it would look like
```spec
Source sha256(<themagicchecksum>)github(signinkeyweexpect): http://someurl
```
This is an orthogonal discussion. you can have multiple variants in both
suggestions of mine (also in the fragmet suffix)
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/463#issuecomment-1635717192
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/463/1635717...@github.com>_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
