Like in Gabble's Bug #46417, Salut should install its non-ABI-stable libraries into a private directory (preventing conflicts over the libwocky.so symlink if Gabble and Salut have incompatible versions of Wocky). With the patches I'll attach here, you can still do something like this: ./configure pluginexeclibdir=/usr/lib/telepathy-android \ pluginexecdir=/usr/lib/telepathy-android/salut if you have a controlled environment where Gabble and Salut are carefully kept in sync. I also fixed a couple of nits in configure.ac which I fixed in Gabble earlier.
Created attachment 58935 [details] [review] [1/4] Avoid Wocky trying to install into --prefix=NONE
Created attachment 58936 [details] [review] [2/4] Avoid non-portable use of += in configure.ac
Created attachment 58937 [details] [review] [3/4] Install non-ABI-stable libraries used by plugins to a private directory
Created attachment 58938 [details] [review] [4/4] Replace plugindir with an AC_ARG_VAR so it can be passed to configure
Yes!
Created attachment 59058 [details] [review] Compile everything before we test it (In reply to comment #5) > Yes! Fixed in git for 0.7.2. Tests pass, except avahi/tubes/two-muc-stream-tubes.py and avahi/file-transfer/receive-file-ipv6.py which hang and need to be interrupted (but that doesn't seem to be a regression, they were already broken). Here's another patch for something that broke while I was testing. I also had to fix some whitespace to get it to pass tests, but I pushed that unreviewed. I don't like what this says about whether people are even bothering to *try* make check...
(In reply to comment #6) > Created attachment 59058 [details] [review] [review] > Compile everything before we test it Looks good. > I also had to fix some whitespace to get it to pass tests, but I pushed that > unreviewed. I don't like what this says about whether people are even bothering > to *try* make check... :-(
(In reply to comment #7) > > Compile everything before we test it > Looks good. Fixed in 0.8.0
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.