So, most of the perl packages that build binary, arch-specific parts, also cause rpm to flag that package as providing that shared library... That only Perl ever needs or knows how to access. e.g. [cweyl@athena Moose-0.71]$ rpmquery --provides perl-Class-MOP MOP.so()(64bit) perl(Class::MOP) = 0.75 perl(Class::MOP::Attribute) = 0.75 perl(Class::MOP::Class) = 0.75 perl(Class::MOP::Immutable) = 0.75 perl(Class::MOP::Instance) = 0.75 perl(Class::MOP::Method) = 0.75 perl(Class::MOP::Method::Accessor) = 0.75 perl(Class::MOP::Method::Constructor) = 0.75 perl(Class::MOP::Method::Generated) = 0.75 perl(Class::MOP::Method::Wrapped) = 0.75 perl(Class::MOP::Module) = 0.75 perl(Class::MOP::Object) = 0.75 perl(Class::MOP::Package) = 0.75 perl(metaclass) = 0.75 perl-Class-MOP = 0.75-1.fc10 perl-Class-MOP(x86-64) = 0.75-1.fc10 [cweyl@athena Moose-0.71]$ rpmquery --provides perl-PerlIO-gzip gzip.so()(64bit) perl(PerlIO::gzip) = 0.18 perl-PerlIO-gzip = 0.18-1.fc10 perl-PerlIO-gzip(x86-64) = 0.18-1.fc10 [cweyl@athena Moose-0.71]$ rpmquery --provides perl-Readonly-XS XS.so()(64bit) perl(Readonly::XS) = 1.04 perl-Readonly-XS = 1.04-11.fc9 [cweyl@athena Moose-0.71]$ Etc, etc. AFAICT, nothing ever requires these libraries; we always specify (automatically or manually) the perl(xxx) provides. Should we be filtering these private libs, to prevent "bad" provides from polluting the repository/rpm metadata? -Chris -- Chris Weyl Ex astris, scientia