@nim-nim: "... define the best dynamic BR strategy over time" is *EXACTLY* the
chicken-egg problem mentioned by @ffesti. Think a bit ...
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Yes --replacefiles just sets a transaction flag bit (equivalent to ".*" but
there are no patterns involved).
By "disable", I mean build all packages without %config or %ghost, avoiding the
need for special handling, and simplifying ima appraisals on embedded devices
(the example given in
The --replacefiles option seems to work on an equivalent of a regex matching
all files (`.*`). You are saying 'What rpm lacks is an ability to apply
--replacefiles to only some of the %config files in the packages being
installed in a single transaction'. What other choice do we have then than
@ffesti You're complicating things unecessary, rpm does not distinguish between
manual and dynamic provides, there's no need to distinguish between manual and
dynamic BuildRequires either
In a dynamic BuildRequires world, the spec still contains static BuildRequires
(sufficient to pull in the
@ignatenkobrain Attempting to fake the state that environment markers check
(and doing so incompletely) is currently causing pain in pipenv:
https://github.com/pypa/pipenv/issues/857
But if you can get pkg_resources to support this natively, then I think that
would be the ideal outcome (and
