Arch Linux

>>sinisterstuff

Thanks!

Say, do want to take over here?
I think you understand this package better than I do.

The symlink is pointing to where the package was built (yaourt's tmp dir) rather than where it would later be installed (the part after "//" is the intended destination). That should probably be fixed in packaging.

As for the library installed in /usr/share/opt, it could also be relocated using the PKGBUILD, but I'm not sure what effect that will have on zeitgeist and chrome (which I don't use).

It's appalling if Ubuntu is still stuck on vim72 but on Arch it's vim74, so in fact the vim plugin doesn't work because it's installed to the wrong place. I made a patch file[1] which changes vim72 to vim74 in the makefile for the vim plugin. You can include it in you tarball and then use it like this:

patches=('vim74.patch')

prepare() {
# apply patches
patch -p1 -d "$srcdir/zeitgeist-datasources" < "$startdir/$patches"
}

prepare() will run before build, so the files get built into the right place. Technically this is a bit fancier than necessary, but makes it easier to include more patches later by just including them in the $patches array (and if I find the time, there'll be more patches). Additionally (personally) I would put all "zeitgeist-datasources" occurrences in the script into a variable to avoid typos.

[1]: vim74.patch https://gist.github.com/sinisterstuf/d2924471185f12e9e1c9

Hi, I get the following warnings with namcap:

zeitgeist-datasources-bzr E: ELF file ('usr/share/opt/google/chrome/resources/zeitgeist_plugin/plugin/libzeitgeist-npapi-plugin.so') outside of a valid path.
zeitgeist-datasources-bzr E: Symlink (usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/xul-ext-zeitgeist) points to non-existing /tmp/yaourt-tmp-sinisterstuf/aur-zeitgeist-datasources-bzr/pkg/zeitgeist-datasources-bzr//usr/share/xul-ext-zeitgeist
zeitgeist-datasources-bzr E: Dependency python detected and not included (programs ['python'] needed in scripts ['usr/bin/zeitgeist-telepathy-observer'])

Indeed, zeitgeist-telepathy-observer has python in the shebang line, so that should probably be included as a dependency in the PKGBUILD.

As for the symlinks, the problem seems to be that they're relative links. They don't seem to be made in the PKGBUILD though, so I suppose if it's an issue at all then it would be more appropriate for me to report it upstream?

Welcome to the modern era, zeitgeist-datasources-bzr.

The software itself needs testing; the package builds with much less fuss.

With either -std=c++11 or -std=gnu++11 build fails:

In file included from ZeitgeistModule.cpp:24:0:
zeitgeist.h:25:44: error: expected initializer before ':' token
class NS_NO_VTABLE NS_SCRIPTABLE zeitgeist : public nsISupports {
^
In file included from /usr/include/c++/4.8.2/new:40:0,
from /usr/include/xulrunner-27.0/nsTArray.h:24,
from /usr/include/xulrunner-27.0/nsStringAPI.h:24,
from ZeitgeistModule.cpp:27:
/usr/include/c++/4.8.2/exception:35:37: error: expected declaration before end of line
#pragma GCC visibility push(default)
^
In file included from ZeitgeistComponent.cpp:24:0:
zeitgeist.h:25:44: error: expected initializer before ':' token
class NS_NO_VTABLE NS_SCRIPTABLE zeitgeist : public nsISupports {

Oops, fixing

You have two arch lines in your PKGBUILD