summaryrefslogtreecommitdiffstats
path: root/docs/manual/adding-packages-python.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/manual/adding-packages-python.txt')
-rw-r--r--docs/manual/adding-packages-python.txt9
1 files changed, 3 insertions, 6 deletions
diff --git a/docs/manual/adding-packages-python.txt b/docs/manual/adding-packages-python.txt
index 8f78f89973..d7ce387778 100644
--- a/docs/manual/adding-packages-python.txt
+++ b/docs/manual/adding-packages-python.txt
@@ -1,8 +1,7 @@
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
-Infrastructure for Python packages
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+=== Infrastructure for Python packages
This infrastructure applies to Python packages that use the standard
Python setuptools mechanism as their build system, generally
@@ -10,8 +9,7 @@ recognizable by the usage of a +setup.py+ script.
[[python-package-tutorial]]
-+python-package+ tutorial
-^^^^^^^^^^^^^^^^^^^^^^^^^
+==== +python-package+ tutorial
First, let's see how to write a +.mk+ file for a Python package,
with an example :
@@ -61,8 +59,7 @@ built.
[[python-package-reference]]
-+python-package+ reference
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+==== +python-package+ reference
As a policy, packages that merely provide Python modules should all be
named +python-<something>+ in Buildroot. Other packages that use the
OpenPOWER on IntegriCloud