Enforcing dependencies between RPMs

[Jason Pyeron]

> -----Original Message-----
> From: Erez Zilber
> Sent: Wednesday, December 30, 2009 8:05
> Subject: Enforcing dependencies between RPMs
> 
> Hi,
> 
> What is the convention for problems like the following?
> 
> I have 2 projects ('A' & 'B'). 'B' is compiled against 
> symbols from 'A'. I have a rpm for 'A' and another rpm for 'B'.
> 
> Now, 'A' & 'B' are installed. I change some symbols in 'A', 
> recreate A.rpm and install the new version of 'A'. When I run 
> 'B' (which was compiled against the old version of 'A'), it 
> fails because 'A' has changed.

B should

Requires: A=1.2.3.4

Then rpm -U A.1.2.3.5.rpm will fail with B needs A.1.2.3.4

* all syntax from memory, please check the rpm docs for exact syntax.

> 
> The question is: how can I enforce that with rpm? What is the 
> convention for such cases?
> 
> Thanks,
> Erez
> _______________________________________________
> Rpm-list mailing list
> Rpm-list at lists.rpm.org
> http://lists.rpm.org/mailman/listinfo/rpm-list
> 




--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-                                                               -
- Jason Pyeron                      PD Inc. http://www.pdinc.us -
- Principal Consultant              10 West 24th Street #100    -
- +1 (443) 269-1555 x333            Baltimore, Maryland 21218   -
-                                                               -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.