Mark and/or Nathan,
What's the idea with rpm dependencies on RHEL5?
I'm getting the following conflicts when trying to install 3.8.5:
pcp-3.8.5-1.el5.x86_64 from /pcp-3.8.5-1.el5.x86_64 has depsolving
problems
--> Missing Dependency: perl-PCP-PMDA = 3.8.5-1.el5 is needed by
package pcp-3.8.5-1.el5.x86_64 (/pcp-3.8.5-1.el5.x86_64)
pcp-3.8.5-1.el5.x86_64 from /pcp-3.8.5-1.el5.x86_64 has depsolving
problems
--> Missing Dependency: python-pcp = 3.8.5-1.el5 is needed by
package pcp-3.8.5-1.el5.x86_64 (/pcp-3.8.5-1.el5.x86_64)
pcp-3.8.5-1.el5.x86_64 from /pcp-3.8.5-1.el5.x86_64 has depsolving
problems
--> Missing Dependency: libmicrohttpd.so.10()(64bit) is needed by
package pcp-3.8.5-1.el5.x86_64 (/pcp-3.8.5-1.el5.x86_64)
Error: Missing Dependency: python-pcp = 3.8.5-1.el5 is needed by
package pcp-3.8.5-1.el5.x86_64 (/pcp-3.8.5-1.el5.x86_64)
Error: Missing Dependency: libmicrohttpd.so.10()(64bit) is needed by
package pcp-3.8.5-1.el5.x86_64 (/pcp-3.8.5-1.el5.x86_64)
Error: Missing Dependency: perl-PCP-PMDA = 3.8.5-1.el5 is needed by
package pcp-3.8.5-1.el5.x86_64 (/pcp-3.8.5-1.el5.x86_64)
I can understand libmicrohttpd could be legitimate dependency
(although I'd argue that if one doesn't give a damn about http access
one should need it) but why create dependency on python-pcp and
perl-PCP-PMDA? I mean you've split them into separate rpm to avoid
dragging perly and snaky bits into an installation which doesn't
need/doesn't care about those bits and yet you have a dependency on
them? What gives?
max
|