On 02/25/2013 02:55 PM, Zdenek Pavlas wrote:
The problem is B has a post install script that calls an executable
installed by C.
Simple requires are always sufficient to guarantee install order,
unless there are dependency loops.
A dependency loop could be detected when ordering the transa
> > The problem is B has a post install script that calls an executable
> > installed by C.
> Simple requires are always sufficient to guarantee install order,
> unless there are dependency loops.
A dependency loop could be detected when ordering the transaction.
Packages participating in the lo
On 02/22/2013 09:06 PM, Kevin Knowles wrote:
Hi all,
I have the following dependency structure:
A depends on B depends on C
The dependencies are being set in each RPM as requires. So, A requires B
and B requires C.
When doing a yum install A, I would expect the install order to always be
C, B
On Fri, 2013-02-22 at 14:06 -0600, Kevin Knowles wrote:
> Hi all,
>
> I have the following dependency structure:
> A depends on B depends on C
>
> The dependencies are being set in each RPM as requires. So, A requires B
> and B requires C.
>
> When doing a yum install A, I would expect the inst
Hi all,
I have the following dependency structure:
A depends on B depends on C
The dependencies are being set in each RPM as requires. So, A requires B
and B requires C.
When doing a yum install A, I would expect the install order to always be
C, B, A. But we are seeing B being installed befor
