Install proper files in obscure build conditions

[sbrabec]

Attached patches fix list of installed files forr various combinations of switches.

avahi-man-selection.patch: Install only man pages to installed binaries.

avahi-no-gtk-no-interfaces.patch: Do not install glade interfaces file, if no gtk is present.

avahi-bookmarks-no-pygtk.patch: Install avahi bookmarks, even if no pygtk is available.

Note: It is still far from sufficient to build system without avahi -> cups -> gtk -> avahi build cycle without a lot of effort.

Over the time, avahi become core part of system, and dependence on gtk2 is not acceptable.

I would propose to split avahi to several sub-projects. openSUSE currently uses: avahi-core avahi compat libraries (several subpackages) avahi-python avahi-python-gtk avahi-utils avahi-utils-gtk avahi-glib avahi-qt3 avahi-qt4 avahi-mono

[sbrabec]

avahi-man-selection.patch

[sbrabec]

avahi-no-gtk-no-interfaces.patch

[sbrabec]

avahi-bookmarks-no-pygtk.patch

[sbrabec]

avahi-no-gtk-python.patch

[sbrabec]

avahi-no-gtk-python.patch: compile python module even without gtk. It seems, that most parts of python are not dependent on gtk+

[sbrabec]

If you will decide to split, here are useful commands:

For creating binding packages with core as a separate and already installed package:

sed -i 's:\(\.\.\|\$(top_builddir)\)/[^/]*/\(lib[^ ]*\.la\):%{_libdir}/\2:g' */Makefile.am

For creating glib/gobject binding package with core as a separate and already installed package:

sed -i 's:libavahi-glib\.la:@@SKIP LIBAVAHI GLIB@@:g
s:\(\.\.\|\$(top_builddir)\)/[^/]*/\(lib[^ ]*\.la\):%{_libdir}/\2:g
s:@@SKIP LIBAVAHI GLIB@@:libavahi-glib.la:g
' */Makefile.am

[lennart]

Hmm, I am not convinced that asplit would be a good idea. I see the advantages, but this would also have one huge disadvantage: it would multiply the amount of work I have with maintaining Avahi. And quite frankly I'd rather reduce it then increase it further.

[lennart]

Finally fixed in r7289ee4.