Web   ·   Wiki   ·   Activities   ·   Blog   ·   Lists   ·   Chat   ·   Meeting   ·   Bugs   ·   Git   ·   Translate   ·   Archive   ·   People   ·   Donate
summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDaniel Narvaez <dwnarvaez@gmail.com>2012-11-25 19:18:29 (GMT)
committer Daniel Narvaez <dwnarvaez@gmail.com>2012-11-25 19:18:29 (GMT)
commit247a259d0c5f1c0c9aa3c3ecbfad0850d658750f (patch)
treeb43e4f1f550a33e9c696692f0d177e827ef444bd
parenta34e0d78c103d38c4c0266ab37d990648356bad8 (diff)
Add a binary snapshots section
-rw-r--r--build.rst30
1 files changed, 30 insertions, 0 deletions
diff --git a/build.rst b/build.rst
index 350967b..92e14e6 100644
--- a/build.rst
+++ b/build.rst
@@ -156,3 +156,33 @@ BUILD_IN_SOURCE
If this is option is set (to any value) all the modules will be built
inside the source directory, even if they support out-of-source builds.
+
+Binary snapshots
+================
+
+Building from sources takes a while and uses a lot of network bandwidth. If
+you just want to test or to develop activities, it might sometimes be more
+convenient to use a binary snapshot. We are building snapshots for each change
+in the source tree, so what you get is built from the very latest code.
+
+First of all download the latest snapshot for your distribution, it's important that you pick the right one, it won't work otherwise.
+
+* `Fedora 17 (32 bit) <http://sugarlabs.org/~dnarvaez/snapshots/fedora-17-32bit/latest>`_
+* `Fedora 17 (64 bit) <http://sugarlabs.org/~dnarvaez/snapshots/fedora-17-64bit/latest>`_
+* `Ubuntu 12.10 (32 bit) <http://sugarlabs.org/~dnarvaez/snapshots/ubuntu-12.10-32bit/latest>`_
+* `Ubuntu 12.10 (64 bit) <http://sugarlabs.org/~dnarvaez/snapshots/ubuntu-12.10-64bit/latest>`_
+
+Then unpack it where you like (adapting the tarball path to your system and
+snapshot filename)::
+
+ tar xfJ ~/Downloads/sugar-snapshot-fedora-17-32bit-1.tar.xz
+
+Enter the directory and run sugar::
+
+ cd sugar-snapshot
+ ./run-sugar.sh
+
+If you are developing activities you should make sure to run setup.py and any
+other command which requires the sugar environment inside a shell. You can run ashell inside an existing terminal with::
+
+ ./run-shell.sh