On Jan 23, 2006, at 11:13 PM, Brian Long wrote:
On Mon, 2006-01-23 at 22:37 +0100, Pim van Riezen wrote:
Wouldn't a declared dependency on foo within bar's specfile satisfy
your needs?
I don't believe so. We typically lay down trigger RPMs to sit idle
with
zero requirements. They only perform actions when the RPM they
trigger
on is installed.
This means bar could be installed first, openssh-server second and foo
last. All of this could happen in Anaconda or yum.
Ooh, shiny feature, I should have figured it wouldn't be that simple.
Can't you change bar and foo to both just run patch on the default
config that ships with openssh? It might take some massaging with
providing a proper context in sshd-config-foo.patch and sshd-config-
bar.patch to make them accept both the vanilla sshd-config _and_ the
one already patched by the other, but it'd certainly get the job done
no matter what order the triggers get called in.
A solution inside the box, of course, would be preferable.
Cheers,
Pi
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
