Description of problem:
The core package contains a heavy dependency on libproxy-python. This subpackage is not needed for core functionality and the %description
| * extremely small core footprint (< 35K)
does not hold either because python is >24MB ;)
Anything which uses the python bindings will have listed them in its Requires:.
Ditto for libproxy-bin; this is a demo program only which is not needed for core functionality.
I am not sure why the explicit Requires: were added but when you want to provide a full-featured standard installation, you might put the libs into a -libs subpackage and create a core package which requires -libs, -python, -bin nd -plugins (see below).
I suggest to package the 'networkmanager' plugin separately (it adds deps on libdbus, is not needed for core functionality and violates %description hence).
Version-Release number of selected component (if applicable):
> * extremely small core footprint (< 35K)
So If you have dependency footprint concern, I would advice you not to build any package against libproxy at all.
using libproxy-libs doesn't make sense.
Requires on libproxy-bin can be avoided.
So, it depends on your use case whether you get a small footprint (core libs + env plugin), or whether you require a huge dependency chain.
A package should support both use cases and avoid unneeded dependencies.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.
More information and reason for this action is here:
libproxy-0.3.1-4.fc13 has been submitted as an update for Fedora 13.
libproxy-0.3.1-4.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update libproxy'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/libproxy-0.3.1-4.fc13
libproxy-0.3.1-4.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.