Merge lp://staging/~dobey/ubuntu/precise/avahi/bring-back-gir into lp://staging/ubuntu/precise/avahi

I tried building this in a pbuilder and got:

make[5]: *** No rule to make target `AvahiCore-0.6.typelib', needed by `all-am'. Stop.

Apparently libgirepository-dev doesn't pull in gobject-introspection, so had to add that too.

Shouldn't AvahiCore.gir be in libavahi-core-dev instead of libavahi-gobject-dev? And a similar split for the gir1.2-* packages right?

When they were packaged from the old gir-repository package before, they were both in gir1.0-avahi-0.6, with the .gir files in gir-repository-dev.

Also, in the source tree, they are both under the avahi-gobject/ directory, and gobject-introspection still requires libgobject to work, even though libavahi-core doesn't. So the gobject-dev package seems to be the most appropriate place in the avahi binary packaging.

Oh, I just realized though. I guess I probably need to Conflicts/Replaces gir-repository-dev from the libavahi-gobject-dev package as well, no?

If you're moving files from one package to another (even if there was a
period when the files were in neither package), please use
Breaks/Replaces rather than Conflicts/Replaces.

I still disagree that it makes sense to bundle the bindings. They have different namespaces and different associated libraries. True, you'll need gobject-introspection to understand the gir, but that is a different thing than needing libavahi-gobject. Imagine an app that only wants to use libavahi-core.

But maybe we need a third opinion.

Well, glib, GTK, GStreamer, and Pango aren't split up in that way for the various different libraries they install, and this preserves the way they used to be packaged in debian from gir-repository. It doesn't seem appropriate, and an app only using avahi-core I think is more likely to use the available static bindings, than use gobject-introspection without also using the GObject-based API.

It seems the manually created AvahiCore-0.6.gir only exists to satisfy the dependency needs of the auto-generated Avahi-0.6.gir. Also, it /is/ Avahi-0.6.gir and not AvahiGObject-0.6.gir, which suggests that for using avahi with gobject-introspection, one really should be using Avahi, and not AvahiCore.

Also, AvahiCore-0.6.gir only includes a few type definitions, and one single function, so probably not useful to use by itself. :)

An update on this: since Debian hasn't included the girs yet, I agree that it doesn't make sense to innovate around the naming ourselves. So I'm OK with the naming for now. But I did notice that when built, the typelib files get put in a multiarch location, which Python does not pick up. That should be looked into.

Could you send your patch to Debian as well? It would be better if they reviewed and merged it there and spare us to have to decide on the binaries to use and the naming

Rodney, could you send it to debian?

No activity from author for a months. Please answer the questions above and mark the branch as needs merging again.

Thanks