Um yes, sure.
You realize that I implemented both %warn and %error in RPM? My comment is
based on re-thinking the usage case of %warn/%error this century.
Fail on %error if you wish.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it
You need to provide better examples, not statements of deficiencies with "macro
files" (which are presumably the files where RPM configuration is defined).
In some sense you are asking a "library" (i.e. macro files) to be able to
reconfigure to satisfy "application" (i.e. rpmbuild ) needs.
A
I think you need to describe a more complete example of what you think needs
additional "freshness" in build root policy scripts: the need cannot be deduced
from the terse descriptions of problems in comment #1.
--
You are receiving this because you are subscribed to this thread.
Reply to this
We have %find_lang thing in RPM, and I don't see any reason why we can't
automatically generate language subpackages. It would be really great
experience for users, it will save space and so on.
IIRC @Conan-Kudo told me one day that openSUSE does it already somehow, so
probably we could adapt
If you want an error message without an actual failure, you can use %{warn:...}
instead of %{error:...}.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Currently macro files have too simple syntax: name and value... For example,
you can't undefine macro, you can't do some conditions and so on. Which makes
macro files not that useful.
One day, @pmatilai said that it would be good to have same syntax everywhere.
--
You are receiving this
@junaruga it stands for `BuildRoot Policy`, scripts which are executed after
build to check (e.g. for RPATH in standard places like /usr/lib). You can find
them here https://github.com/rpm-software-management/rpm/tree/master/scripts
(with `brp-` prefix). But those are really basic.
--
You are
What is brp script's "brp"? Though it may be basic knowledge.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Nowadays, buildroot policy is something way more complicated than it used to be
10 years ago. We need to be able to run brp scripts depending on files which
are in buildroot (something similar to dependency generators), depending on
tools which are available (e.g. it doesn't make any sense to
Reopened #190.
--
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/190#event-1215322179___
Rpm-maint mailing list
Closed #190.
--
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/190#event-1215322143___
Rpm-maint mailing list
11 matches
Mail list logo
