Once upon a time, D Canfield <[EMAIL PROTECTED]> said:
> The problem is that older versions of these modules are included in
> the main perl RPM. So, even though I have newer subpackages that I
> could recompile, they will conflict with perl itself. And yes, I
> could just build the packages with CPAN, but that defeats the purpose
> of RPM in the first place.
Are you sure they'll actually conflict? Multiple RPMs can have the same
virtual provides; conflicts only come when the files overlap I believe.
Since the module included with perl is in the base perl directory and
any module you build will go in site_perl (or vendor_perl if you use
cpanspec), there should be no file conflicts.
Also, perl will look in site_perl/vendor_perl for modules before the
base directory, so that shouldn't be a problem either.
The only problem you might have would be with any man pages; the easiest
solution would be to exclude them from your RPM ("perldoc <module>" will
follow the same search path as perl itself).
--
Chris Adams <[EMAIL PROTECTED]>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
