Wouldn't this also make sense for `%sourcelist` too?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
>every single typo stands out
Which I would consider a good thing, because then I can fix the spello.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@vathpela pushed 1 commit.
ef44ff173f42517ebebfe5b31c35e3bd1e9c6388 Make "%patchlist -f patches" work.
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
I noticed a change in the functioning of rpmbuild with the option --nobuild
activated. I use this option to check the spec file but also to check
unsatisfied build dependencies. In the previous version "rpmbuild --nobuild"
would check the build requirements but not in version 4.15.
I have
This adds a -f argument to %patchlist, similar to that for %files.
There is no limit to how many patchlist files you specify, and doing so
does not restrict the use of an inline patch list. Patches get added
from the leftmost list to rightmost, and any patches listed below get
added after that.
While debugging something else, I noticed that when I run rpmbuild,
valgrind says:
==189844==
==189844== HEAP SUMMARY:
==189844== in use at exit: 12,088 bytes in 45 blocks
==189844== total heap usage: 61,336 allocs, 61,291 frees, 28,975,297 bytes
allocated
==189844==
==189844== 24 bytes in
"p" is used for this purpose throughout the code otherwise, please stick with
that. Calling it "position" all of a sudden makes it look like something
entirely different and somehow more important due to the longer name.
https://www.kernel.org/doc/html/v4.10/process/coding-style.html#naming is
Case `%triggerin -- %{name} < 1.0-2.new`:
RPM triggers `%triggerin -- %{name} < 1.0-2.new`. It is according to the
description in the documentation [1] (_The %triggerin script is also run when
your package_ (`baz-1.0-2.new`) _is installed or upgraded, should the target
package_
