summaryrefslogtreecommitdiff
path: root/development/Pivy/README
diff options
context:
space:
mode:
authorAleksandar Samardzic <asamardzic@gmail.com>2010-05-12 17:38:13 +0200
committerRobby Workman <rworkman@slackbuilds.org>2010-05-12 17:38:13 +0200
commitcd6705175cb352300a1eb2cf15e0925ce0f3b625 (patch)
tree168513a40a13ad25153f25a9d24d3c07962ac32c /development/Pivy/README
parentf4a23c5a024e2cda67b2135e9aa2660bad2a1233 (diff)
downloadslackbuilds-cd6705175cb352300a1eb2cf15e0925ce0f3b625.tar.gz
development/Pivy: Updated for version 20081227
Diffstat (limited to 'development/Pivy/README')
-rw-r--r--development/Pivy/README20
1 files changed, 19 insertions, 1 deletions
diff --git a/development/Pivy/README b/development/Pivy/README
index a1bc2ffef6..d16604e664 100644
--- a/development/Pivy/README
+++ b/development/Pivy/README
@@ -8,5 +8,23 @@ Pivy allows:
* incorporation of Scripting Nodes into the scene graph which are
capable of executing Python code and callback functions
+This script is tested using the svn code from 20081227, and this is
+the tarball hosted on our site. You may elect to use this source code
+to build the package, or you can pull the latest from their subversion
+repository as indicated below.
+
+If you want to use the latest subversion source when building your
+Pivy package, you will need to get it from their svn server. To get
+the source code, you can use the included "Pivy-mksrctarball.sh"
+script, which will to download the source code and create a compressed
+tarball of it using the date (date +"%Y%m%d") as its version string.
+
+If you have already Pivy's source code as a tarball, for example:
+Pivy-20081227.tar.bz2
+You can tell the build script to use it with the following command:
+VERSION=20081227 ./Pivy.SlackBuild
+Note that this is the version that will be used by default unless you
+specify otherwise.
+
Pivy package depends on Coin and SWIG packages, both available from
-SlackBuilds.org. \ No newline at end of file
+SlackBuilds.org.