On Mon, 2006-01-23 at 22:37 +0100, Pim van Riezen wrote:
> On Jan 23, 2006, at 10:33 PM, Brian Long wrote:
>
> > The reason I do this is because we have a global sshd_config on all
> > hosts. We want to replace one config variable only on certain
> > machines.
> > We could duplicate the entire sshd_config in the third RPM, but then
> > we'd have dual maintenance just to maintain the difference of one
> > config
> > variable.
> >
> > Does anyone know what we might be doing wrong or how we might better
> > accomplish this task?
> >
> > Triggers should fire in this order:
> > openssh-server -> foo -> bar
>
> 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.
/Brian/
--
Brian Long | | |
IT Data Center Systems | .|||. .|||.
Cisco Linux Developer | ..:|||||||:...:|||||||:..
Phone: (919) 392-7363 | C i s c o S y s t e m s
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
