Marko,
I'm afraid you cannot simply do this ...
commit 7a975d2b739aff75c9b2241c3b80cfb3613b6a78
Author: Marko Myllynen <myllynen@xxxxxxxxxx>
Date: Mon Jul 11 08:37:23 2016 +1000
build: add to ds389{,log} RPM package dependencies
Resolves RH BZ# 1354055
because perl-LDAP is not available as an rpm package for all platforms
where we build PCP rpms, and in these cases we have the option of
installing Net::LDAP via cpan so the PMDA works even when the rpm prereq
is not satisified.
So this change breaks the installs on those platforms (I have 2 of 'em
so far in my QA Farm).
I believe the correct way to address this sort of issue is either:
(a) add configure glue to detect if the PMDA should be built and
packaged, then use a
%if "@enable_mypmda@" == "true"
guard in the rpm spec file, or
(b) if the Requires/BuildRequires prereq is needed but only safe on some
distros, then use something like
%if 0%{?rhel} > 5
as a guard in the rpm spec file
Of course (a) is preferred.
The perl-Date-Manip one seems safer as that would appear to be more
widely available.
I've reverted the perl-LDAP one in my tree.
|