From: Harvie <tomas@mudrunka.cz>
Date: Wed, 2 Jun 2010 03:25:47 +0000 (+0200)
Subject: first commit
X-Git-Url: https://git.harvie.cz/?a=commitdiff_plain;h=30e27dcddb95e6147ea4e24080f38ea2f05988a1;p=mirrors%2Flibpurple-core-answerscripts.git

first commit
---

30e27dcddb95e6147ea4e24080f38ea2f05988a1
diff --git a/README b/README
new file mode 100644
index 0000000..60ef349
--- /dev/null
+++ b/README
@@ -0,0 +1,28 @@
+libPurple core-answerscripts plugin
+	Framework for hooking scripts to received messages for various libpurple clients
+
+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 :
+	You can compile the plugin using
+	$ make
+	and install it with
+	$ make install
+	This will install it in ~/.purple/plugins so that only the user who install it can use it.
+	$ make user
+	Install main script and sample answerscripts to ~/.purple/answerscripts.d/
+
+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".