[Bug 29070] Should install .vapi in the usual place or document non-standard usage

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=29070

--- Comment #2 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2010-07-16 03:06:38 PDT ---
(In reply to comment #1)
> > Offering a .pc file to put the vapi directory onto the path seems to be highly
> > unconventional (I haven't seen any evidence of it in Debian), so if there's a
> > compelling reason to do this, it should be documented somewhere.
> 
> I thought it would be handy to confirm at configure-time whether the
> telepathy-glib Vala bindings are installed. But it looks like we can just check
> for the file in $(pkg-config --variable=vapidir vala-1.0). So we can just cut
> the telepathy-glib.pc file.
> 
> I've done that in this new branch. Please review and if you approve. I bump the
> nano version so libfolks can depend upon this version.

> -m4_define([tp_glib_nano_version], [1])
> +m4_define([tp_glib_nano_version], [2])

I'd prefer not to have libfolks depend on an unreleased telepathy-glib. We can
do that without adding extra cruft, by doing the telepathy-glib change in two
stages:

* change telepathy-glib to install in the normal vapidir, but still install
telepathy-vala.pc, with the following change:

-vapidir=@datadir@/telepathy/vapi
-valaflags=--vapidir=${vapidir}
+vapidir=@datadir@/vala/vapi
+valaflags=

* (time passes)

* release telepathy-glib 0.11.11 with that change, which does not break the
existing libfolks

* in libfolks git, bump the dependency to 0.11.11 and make it ignore
telepathy-vala.pc

* (time passes)

* release libfolks 0.1.n with that change

* delete telepathy-vala.pc

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.