--- a/cwconfig.py Fri Jul 04 14:28:26 2014 +0200
+++ b/cwconfig.py Fri Jul 04 14:37:08 2014 +0200
@@ -124,14 +124,14 @@
Python
``````
-If you installed *CubicWeb* by cloning the Mercurial forest or from source
+If you installed *CubicWeb* by cloning the Mercurial shell repository or from source
distribution, then you will need to update the environment variable PYTHONPATH by
-adding the path to the forest `cubicweb`:
+adding the path to `cubicweb`:
Add the following lines to either :file:`.bashrc` or :file:`.bash_profile` to
configure your development environment ::
- export PYTHONPATH=/full/path/to/cubicweb-forest
+ export PYTHONPATH=/full/path/to/grshell-cubicweb
If you installed *CubicWeb* with packages, no configuration is required and your
new cubes will be placed in `/usr/share/cubicweb/cubes` and your instances will
--- a/doc/book/en/admin/cubicweb-ctl.rst Fri Jul 04 14:28:26 2014 +0200
+++ b/doc/book/en/admin/cubicweb-ctl.rst Fri Jul 04 14:37:08 2014 +0200
@@ -37,7 +37,7 @@
cubicweb-ctl newcube
This will create a new cube in
-``/path/to/forest/cubicweb/cubes/<mycube>`` for a Mercurial forest
+``/path/to/grshell-cubicweb/cubes/<mycube>`` for a Mercurial
installation, or in ``/usr/share/cubicweb/cubes`` for a debian
packages installation.
--- a/doc/book/en/annexes/depends.rst Fri Jul 04 14:28:26 2014 +0200
+++ b/doc/book/en/annexes/depends.rst Fri Jul 04 14:37:08 2014 +0200
@@ -6,7 +6,7 @@
=========================
When you run CubicWeb from source, either by downloading the tarball or
-cloning the mercurial forest, here is the list of tools and libraries you need
+cloning the mercurial tree, here is the list of tools and libraries you need
to have installed in order for CubicWeb to work:
* yapps - http://theory.stanford.edu/~amitp/yapps/ -
--- a/doc/book/en/annexes/mercurial.rst Fri Jul 04 14:28:26 2014 +0200
+++ b/doc/book/en/annexes/mercurial.rst Fri Jul 04 14:37:08 2014 +0200
@@ -18,13 +18,13 @@
.. _Mercurial: http://www.selenic.com/mercurial/
-In contrast to CVS/Subversion, we usually create a repository by
+In contrast to CVS/Subversion, we usually create a repository per
project to manage.
In a collaborative development, we usually create a central repository
accessible to all developers of the project. These central repository is used
-as a reference. According to its needs, then everyone can have a local repository,
-that you will have to synchronize with the central repository from time to time.
+as a reference. According to their needs, everyone can have a local repository,
+that they will have to synchronize with the central repository from time to time.
Major commands
@@ -33,7 +33,7 @@
hg clone ssh://myhost//home/src/repo
-* See the contents of the local repository (graphical tool in Tk)::
+* See the contents of the local repository (graphical tool in Qt)::
hgview
@@ -111,17 +111,15 @@
3. `hg ci`
4. `hg push`
-Installation of the forest extension
-````````````````````````````````````
+Installation of the guestrepo extension
+```````````````````````````````````````
-Set up the forest extension by getting a copy of the sources
-from http://hg.akoha.org/hgforest/ and adding the following
+Set up the guestrepo extension by getting a copy of the sources
+from https://bitbucket.org/selinc/guestrepo and adding the following
lines to your ``~/.hgrc``: ::
[extensions]
- hgext.forest=
- # or, if forest.py is not in the hgext dir:
- # forest=/path/to/forest.py
+ guestrepo=/path/to/guestrepo/guestrepo
More information
--- a/doc/book/en/tutorials/base/customizing-the-application.rst Fri Jul 04 14:28:26 2014 +0200
+++ b/doc/book/en/tutorials/base/customizing-the-application.rst Fri Jul 04 14:37:08 2014 +0200
@@ -26,7 +26,7 @@
cubicweb-ctl newcube myblog
-This will create in the cubes directory (:file:`/path/to/forest/cubes` for source
+This will create in the cubes directory (:file:`/path/to/grshell/cubes` for source
installation, :file:`/usr/share/cubicweb/cubes` for Debian packages installation)
a directory named :file:`blog` reflecting the structure described in
:ref:`cubelayout`.