240 ----------------------------------- |
240 ----------------------------------- |
241 |
241 |
242 To keep-up with on-going development, clone the :ref:`Mercurial |
242 To keep-up with on-going development, clone the :ref:`Mercurial |
243 <MercurialPresentation>` repository:: |
243 <MercurialPresentation>` repository:: |
244 |
244 |
245 hg clone -u stable http://hg.logilab.org/cubicweb # stable branch |
245 hg clone -u 'last(tag())' http://hg.logilab.org/cubicweb # stable version |
246 hg clone http://hg.logilab.org/cubicweb # development branch |
246 hg clone http://hg.logilab.org/cubicweb # development branch |
247 |
247 |
248 To get many of CubicWeb's dependencies and a nice set of base cubes, run the |
|
249 `clone_deps.py` script located in `cubicweb/bin/`:: |
|
250 |
|
251 python cubicweb/bin/clone_deps.py |
|
252 |
|
253 (Windows users should replace slashes with antislashes). |
|
254 |
|
255 This script will clone a set of mercurial repositories into the |
|
256 directory containing the ``cubicweb`` repository, and update them to the |
|
257 latest published version tag (if any). |
|
258 |
|
259 .. note:: |
|
260 |
|
261 In every cloned repositories, a `hg tags` will display a list of |
|
262 tags in reverse chronological order. One reasonnable option is to go to a |
|
263 tagged version: the latest published version or example, as done by |
|
264 the `clone_deps` script):: |
|
265 |
|
266 hg update cubicweb-version-3.12.2 |
|
267 |
|
268 Make sure you also have all the :ref:`InstallDependencies`. |
248 Make sure you also have all the :ref:`InstallDependencies`. |
269 |
|