On Wed, Nov 12, 2014 at 03:35:43PM +0100, Jan Pazdziora wrote:
On Wed, Nov 12, 2014 at 03:02:43PM +0100, Jakub Hrozek wrote:
> On Wed, Nov 12, 2014 at 02:48:28PM +0100, Jan Pazdziora wrote:
> > I think Requires(pre) is the recommended syntax these days. It helps
> > people remember that they can also use it for other scriptlet times if
> > they need to.
> Hmm, doesn't Requires(pre) specify what is required for the %pre
Right. I thought that's what you wanted. The point is, pure Requires
merely states what requirements should be fulfilled once the
transaction finishes. By using Requires(...), you state requirement
for the particular phase of the transaction.
Sorry, I was ambiguous. What we have now is a dependency like this:
sssd-krb5 -- sssd-krb5-common -- sssd-common
In some cases, I saw that yum/RPM installed sssd-krb5-common first and
only then sssd-common. This breaks because sssd-krb5-common needs a user
that was going to be created in sssd-common's %pre.
Sumit was correct that on the source level we have a strange cycle, but
I don't see that cycle being propagated into the RPM level -- I was able
to install sssd-common w/o sssd-krb5-common just fine ...
Useful for cleanup as well when in %post you want to run something
that might have been erased by the same transaction.
Principal Software Engineer, Identity Management Engineering, Red Hat
sssd-devel mailing list