summaryrefslogtreecommitdiff
path: root/libre/xsp/xsp.install
diff options
context:
space:
mode:
authorroot <root@rshg054.dnsready.net>2013-03-23 00:06:21 -0700
committerroot <root@rshg054.dnsready.net>2013-03-23 00:06:21 -0700
commita42cd7aaabfdb3ecc0a538548e8dbcc7ca860b2d (patch)
treebbea919c4d1e7d8d747e636040d0cd510c279d68 /libre/xsp/xsp.install
parent6b3123e5628817e3cef9c44989dffd21c49b0817 (diff)
Sat Mar 23 00:06:20 PDT 2013
Diffstat (limited to 'libre/xsp/xsp.install')
-rw-r--r--libre/xsp/xsp.install37
1 files changed, 37 insertions, 0 deletions
diff --git a/libre/xsp/xsp.install b/libre/xsp/xsp.install
new file mode 100644
index 000000000..d2cc5955a
--- /dev/null
+++ b/libre/xsp/xsp.install
@@ -0,0 +1,37 @@
+# arg 1: the new package version
+post_install() {
+ cat << EOM
+
+--> xsp is just the helping app for mod_mono if you like a production like
+--> server. xsp itself is for ASP testing mainly -- read the manpage for xsp
+--> to know which options are available.
+--> Parabola will provide xsp configured by a .webapp configuration file
+--> which rests in /etc/xsp. Just put your other webapp files there to let
+--> xsp pick them up.
+--> xsp is commandline based configuration is done in /etc/conf.d/xsp. Set all
+--> your arguments there. Don't forget that you can run xsp from the console
+--> as oridinary user, which is safer and for testing absolutely sufficient!!
+
+--> You can run the testpages simply by starting the server and calling
+ http://localhost:8080
+--> from your browser's location bar
+
+
+EOM
+}
+
+# arg 1: the new package version
+# arg 2: the old package version
+post_upgrade() {
+ post_install $1
+}
+
+# arg 1: the old package version
+pre_remove() {
+ /bin/true
+}
+
+# arg 1: the old package version
+post_remove() {
+ /bin/true
+}