OrderWithRequires(pre) would probably be better for the use case which is
described in this PR, but OrderWithRequires without pre also worked. This is
probably some undocumented behaviour in dependency resolution, probably it
tries to install required packages before the package which requires
This is indeed not possible. The argument here is (except that it is simply not
implemented) that those dependencies are generated from files in the package
and not the scriptlets. So qualifiers should not be needed. But I am pretty
sure people could come up with some valid use cases.
There is
Thanks. One question: do I understand correctly that currently there is no way
to make a generator of Requires(pre), Requires(post), Requires(postun),
OrderWithRequires(pre) etc.?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
Yes, not having a dependency generator for OrderWithRequires is clearly an
oversight. Details on what generators are a valid use case are not relevant
here.
Thanks for the patch!
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
Merged #1257 into master.
--
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/1257#event-3424224260___
Rpm-maint mailing list
> But why? If a package contains a config is /usr/lib/sysusers.d/, why not to
> ensure that it is installed after systemd-sysusers binary is present and so
> the scriptlet which creates users can be executed?
Yes, in that case the dependency is warranted.
> If there is just a scriptlet which
If there is just a scriptlet which calls `systemctl preset`, in _some_ cases it
may silently fail to enable a service which must be enabled.
In most cases, I agree, it is not needed, but seems to be not harmful.
--
You are receiving this because you are subscribed to this thread.
Reply to this
But why? If a package contains a config is /usr/lib/sysusers.d/, why not to
ensure that it is installed after systemd-sysusers binary is present and so the
scriptlet which creates users can be executed?
--
You are receiving this because you are subscribed to this thread.
Reply to this email
> it is only some specific cases where this needs to be used.
Yeah, we used to pull in systemd much more often. Nowadays, most packages
should not pull in systemd, and install time ordering also doesn't matter. But
that's largely irrelevant here, since systemd was only used as an example here.
> When a package contains a systemd unit, %systemd_* macros are usually used;
> it is usefull to add "OrderWithRequires: systemd" in this case to ensure
> that systemd is installed before that package.
I think I disagree here, it is only some specific cases where this needs to be
used.
cc
It was possible to generate Requires, Recommends etc. using external dependency
generators.
Adding ability to generate OrderWithRequires.
Example use case:
When a package contains a systemd unit, %systemd_* macros are usually used;
it is usefull to add OrderWithRequires: systemd in this case to
11 matches
Mail list logo
