Closed #1350.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1350#event-3702978603___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Works awesome, thank you Michal, you rock!!
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1350#issuecomment-682405869___
Rpm-ma
@dmnks commented on this pull request.
> } else {
- patchcmd = rpmExpand("%{__patch} ", args, " < ", fn, NULL);
+ patchcmd = rpmExpand("RPM_PATCH_NAME=", sp->path, " %{__patch} ", args,
" < ", fn, NULL);
`sp->path` is the same as `fn`, and it's what's passed to `stdin` of the
Thinking about your use case, you can achieve the same (i.e. get the filename
of the patch being passed) just by running
`readlink -f /dev/stdin`
in your `%__patch` script. No need to patch RPM after all :)
--
You are receiving this because you are subscribed to this thread.
Reply to this email
when people override %__patch, they are able to process the patch name
now with this change
we need this change for creating repositories with expanded sources for CentOS
Stream.
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull
