The python packaging guidelines include a pointer to
http://fedoraproject.org/wiki/Packaging:AutoProvidesAndRequiresFiltering#Arch-specific_extensions_to_scripting_languages,
which includes an example for python packages to avoid provides for
arch-specific shared objects in the sitearch hierarchy.
I was doing a local build of limxml2 and added filtering for the
libxml2mod.so object in the libxml2-python sub-package. However, when I
came to update to my local build I ran into a dependency issue because
python-dmidecode actually requires libxml2mod.so (and libxml2-python is
the only thing that currently provides it).
I don't know the specifics of the relationship between python-dmidecode
and libxml2-python, so I'd like to ask:
1. Is it *always* right to filter provides for private shared objects,
or are exceptions like this quite common, or
2. If this is not a real dependency, what should packages like
python-dmidecode do to avoid them? Is it due to unnecessary linking perhaps?
Paul.
--
packaging mailing list
packaging@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/packaging
