Bug 189399
Summary: | [ENH] avahi-python files in separate RPM | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dan Williams <dcbw> |
Component: | avahi | Assignee: | Lennart Poettering <lpoetter> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | bnocera, erik, frankly3d, kparal, louiz, stijn |
Target Milestone: | --- | Keywords: | EasyFix, FutureFeature, Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-09-17 17:08:49 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1267197 |
Description
Dan Williams
2006-04-19 18:36:17 UTC
Right, so it's in avahi-tools package already, but perhaps it should be an 'avahi-python' RPM instead? The avahi-python modules seem to be really developed purely as a library for use by the avahi-tools, most of which are python scripts. I'm not sure it really makes sense to distribute the avahi-python modules in a separate RPM, as if they were intended to be a general purpose python API to avahi services, beyond providing limited services to the tools - there is no documentation for them for a start. Unless there is a really good reason why we need the avahi-python modules in a separate RPM, I think they should remain part of avahi-tools - is there ? I can't see a good reason to ship these python scripts separately to avahi-tools - if you disagree, please re-open and provide a reason - closing out. Reopening, I have a good reason. There are some programs out there which make use of avahi python files. One good example is Gajim (packaged as gajim). If I want to install gajim, it currently requires avahi-ui-tools, i.e. I end up with three extra icons in my system menu (Avahi SSH Server/VNC Server/Zeroconf Browser). I don't really want those tools to be there, I don't use them and they just clutter my application menu. If you look at Debian, they have also separated python files from UI tools: http://packages.debian.org/sid/i386/avahi-ui-utils/filelist http://packages.debian.org/sid/i386/python-avahi/filelist Please create python-avahi in Fedora as well, so that applications don't have to pull UI tools needlessly. Totem's airplay plugin have requirements on avahi's Python bindings too. I wanted to use http://www.avahi.org/wiki/Examples/PythonPublishAlias but it failed to 'import avahi', which led me to this bug. Please package the python bindings separately. This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19 Not urgent but it would improve testing of: http://james.fedorapeople.org/yum/avahi/ Mandos also requires the avahi python binding. There is no official Mandos package for Fedora yet but I am trying to contribute one. Requireing avahi-ui-tools is currently the only way to get it to work, and that pulls in quite a list of other packages: Installing: avahi-ui-tools Installing for dependencies: at-spi2-atk at-spi2-core avahi-glib avahi-ui-gtk3 cairo-gobject colord-libs fltk gtk3 libXevie libglade2 libgusb pycairo pygtk2 pygtk2-libglade tigervnc tigervnc-icons tigervnc-license The assignee seems to no longer exist, for some reason the field wasn't reset. Trying to do that now. This is fixed with avahi 0.6.31-36. A python-avahi and python3-avahi packages are provided. *** This bug has been marked as a duplicate of bug 1260432 *** |