Perl arch specific packages often contain shared libraries that are private to Perl, and ought not to be publicized as "provides" for a package. Can we apply the following patch to the Perl spec template, please? This will filter the private libs from ever being scanned by the rpm "provides" generator. --- XXXX 26 Feb 2009 12:39:28 -0000 1.9 +++ XXXX 28 Feb 2009 22:57:42 -0000 @@ -17,2 +17,7 @@ +# don't "provide" private Perl libs +%global _use_internal_dependency_generator 0 +%global provfind /bin/sh -c "grep -v '%perl_vendorarch.*\\.so$' | %__find_provides" +%global __find_provides %provfind + %description
I don't think it's appropriate to uglify spec files or templates with things like this. Instead, if this is a problem, it should be fixed in rpmbuild. And I don't think this is perl specific, at least python and possibly ruby and some other things are in the same boat.
Do you have a suggestion as to how to do this, addressing the issue at hand, that's less aesthetically abusive to you? I'll ask that rpmbuild address it, but given their historical resistance to even filtering out the bits in %{_docdir}, I rather suspect it's going to be a no-go.