libPurple core-answerscripts plugin
- Framework for hooking scripts to received messages for various libpurple clients
+ - Framework for hooking scripts to respond received messages for various libpurple clients such as pidgin or finch
+ - This simple plugin just passes every single message received by any libPurple-based client (pidgin,finch) to sript(s) in user's home directory... So you can add various hooks to your pidgin or finch without need of writing and compiling own C plugin or messing with buggy perl plugin and restarting client after each change in plugin.
+ - There are already few sample (answer)scripts in purple directory, so you can check how easy it is to write some script for pidgin or finch...
-This simple plugin just passes every single message received by any libPurple-based client (pidgin,finch) to sript(s) in user's home directory... So you can add various hooks to your pidgin or finch without need of writing and compiling own C plugin or messing with buggy perl plugin and restarting client after each change in plugin.
-
-There are already few sample (answer)scripts in purple directory, so you can check how easy it is to write some script for pidgin or finch...
-
-
-The libpurple header files are needed to compile the plugin.
Building & installation:
-To build and install :
+- The libpurple header files are needed to compile the plugin.
+
+- To build and install :
You can compile the plugin using
$ make
and install it with
$ make user
Install main script and sample answerscripts to ~/.purple/answerscripts.d/
-To install it for everybody on your computer,
+- To install it for everybody on your computer,
$ make
$ su
- # make install PREFIX="/path/to/pidgin" (this command as root user)
- generally /path/to/pidgin is /usr or /usr/local. If you don't know the path then you can find out using
- $ whereis pidgin
- and look for the part before "/lib/pidgin".
+ # make install PREFIX="/path/to/libpurple" (this command as root user)
+ generally /path/to/libpurple is /usr or /usr/local. If you don't know the path then you can find out using
+ $ whereis libpurple
+ and look for the part before "/lib/libpurple.so".
+
+
+Installing from packages:
+ - ArchLinux: http://aur.archlinux.org/packages.php?ID=37942
--- /dev/null
+# Contributor: Thomas Mudrunka <harvie@@email..cz>
+# Maintainer: Thomas Mudrunka <harvie@@email..cz>
+# You can also contact me on http://blog.harvie.cz/
+
+pkgname=libpurple-core-answerscripts-git
+pkgver=20100609
+pkgrel=1
+pkgdesc="Framework for hooking scripts to respond received messages for various libpurple clients such as pidgin or finch"
+arch=('x86_64' 'i686')
+url="http://github.com/harvie/libpurple-core-answerscripts"
+license=('GPL')
+depends=('libpurple')
+makedepends=('git')
+source=()
+md5sums=()
+
+_gitroot='git://github.com/Harvie/libpurple-core-answerscripts.git'
+_gitname="$pkgname"
+
+build() {
+ cd ${srcdir}/
+
+ cd "$srcdir"
+ msg "Connecting to GIT server...."
+
+ if [ -d $_gitname ] ; then
+ cd $_gitname && git pull origin
+ msg "The local files are updated."
+ else
+ git clone $_gitroot $_gitname
+ fi
+
+ msg "GIT checkout done or server timeout"
+ msg "Starting make..."
+
+ rm -rf "$srcdir/$_gitname-build"
+ cp -r "$srcdir/$_gitname" "$srcdir/$_gitname-build"
+ cd "$srcdir/$_gitname-build"
+
+ #
+ # BUILD HERE
+ #
+
+ make || return 1
+ make install PREFIX="$pkgdir/usr" || return 1
+}