@@ -43,7 +43,9 @@ If no such file is found, the :ref:`ref-tasks-compile` task does nothing.
``do_compile_ptest_base``
-------------------------
-Compiles the runtime test suite included in the software being built.
+As defined in the :ref:`ref-classes-ptest` class, this task simply calls
+``do_compile_ptest()``, which any ptest-enabled recipe is expected to
+define for compiling its associated ptest package.
.. _ref-tasks-configure:
@@ -65,7 +67,10 @@ file is found or the :term:`CLEANBROKEN` variable is set to "1", the
``do_configure_ptest_base``
---------------------------
-Configures the runtime test suite included in the software being built.
+As defined in the :ref:`ref-classes-ptest` class, this task simply calls
+``do_configure_ptest()``, which any ptest-enabled recipe is expected to
+define for configuring its associated ptest package. Very few recipes need
+to define their own ``do_configure_ptest()`` function.
.. _ref-tasks-deploy:
@@ -198,8 +203,21 @@ that either directly or indirectly depend on the installed files (e.g.
``do_install_ptest_base``
-------------------------
-Copies the runtime test suite files from the compilation directory to a
-holding area.
+As defined in the :ref:`ref-classes-ptest` class, this task contains generic
+installation code that will be invoked for all ptest-enabled recipes,
+in the midst of which this task calls the ``do_install_ptest()`` function
+that would be defined by any ptest-enabled recipe if that recipe needs to
+define any *additional* recipe-specific installation processing::
+
+ do_install_ptest_base() {
+
+ ... snip ...
+
+ do_install_ptest
+
+ ... snip ...
+
+ }
.. _ref-tasks-package:
Be a little more forthcoming about how the "do_*_ptest_base" tasks work. Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> ---