kallithea Changeset - 855ba1f07aeb

Changeset - 855ba1f07aeb

Parent rev.

Child rev.

[Not reviewed]

default

0 1 0

Andrew Shadura - 10 years ago 2016-07-12 23:33:11
andrew@shadura.me

docs: use ., not source, as the user isn't guaranteed to have it

Even though bash is the default shell nearly everywhere, a restricted
user running Kallithea doesn't necessarily have it as the default,
so better use POSIX-compatible . command. Besided, it's also shorter.

1 file changed with 2 insertions and 2 deletions:

docs/installation.rst

0 comments (0 inline, 0 general)

docs/installation.rst

➞

Show inline comments

@@ @@ -51,13 +51,13 @@ Installation from repository source @@
 To install Kallithea in a virtualenv_ using the stable branch of the development
 repository, follow the instructions below::
         hg clone https://kallithea-scm.org/repos/kallithea -u stable
         cd kallithea
         virtualenv ../kallithea-venv
-        source ../kallithea-venv/bin/activate
+        . ../kallithea-venv/bin/activate
         pip install --upgrade pip setuptools
         pip install -e .
         python2 setup.py compile_catalog   # for translation of the UI
 You can now proceed to :ref:`setup`.
@@ @@ -78,13 +78,13 @@ An additional benefit of virtualenv_ is @@
     virtualenv /srv/kallithea/venv
 - Activate the virtualenv_ in your current shell session and make sure the
   basic requirements are up-to-date by running::
-    source /srv/kallithea/venv/bin/activate
+    . /srv/kallithea/venv/bin/activate
     pip install --upgrade pip setuptools
 .. note:: You can't use UNIX ``sudo`` to source the ``virtualenv`` script; it
    will "activate" a shell that terminates immediately. It is also perfectly
    acceptable (and desirable) to create a virtualenv as a normal user.

0 comments (0 inline, 0 general)