Skip to content
Snippets Groups Projects
Commit 4b5354f3 authored by André Anjos's avatar André Anjos :speech_balloon:
Browse files

Doc improvements

parent 0161786b
No related branches found
No related tags found
1 merge request!29Issue 25
Pipeline #
...@@ -24,7 +24,6 @@ development of your own package, and which we normally ship with all ...@@ -24,7 +24,6 @@ development of your own package, and which we normally ship with all
[scripts] [scripts]
recipe = bob.buildout:scripts recipe = bob.buildout:scripts
dependent-scripts = true
Replace ``<PACKAGE>`` by your package name and you should be ready to run the Replace ``<PACKAGE>`` by your package name and you should be ready to run the
......
...@@ -47,9 +47,12 @@ first.cfg``: ...@@ -47,9 +47,12 @@ first.cfg``:
$ buildout -c first.cfg $ buildout -c first.cfg
Slightly modify ``buildout.cfg`` from ``bob.extension`` to include a new line The previous command should not download anything from PyPI_ and will create a
in the ``buildout.develop`` entry before ``.``, so the new buildout will also symbolic egg link in ``develop-eggs`` called ``bob.buildout.egg-link``. To make
take the bootstrapped buildout into consideration. It should look like this: sure your ``first.cfg`` bootstrap procedure worked, check there. Now, slightly
modify ``buildout.cfg`` from ``bob.extension`` to include a new line in the
``buildout.develop`` entry before ``.``, so the new buildout will also take the
bootstrapped buildout into consideration. It should look like this:
.. code-block:: sh .. code-block:: sh
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment