Skip to content

Commit efed104

Browse files
authored
Increase level of MPI subsection headers
1 parent 4ff3d85 commit efed104

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/maintainer/knowledge_base.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -488,7 +488,7 @@ and apply the appropriate conditionals in your build:
488488
489489
490490
Preferring a provider (usually nompi)
491-
"""""""""""""""""""""""""""""""""""""
491+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
492492

493493
Up to here, mpi providers have no explicit preference. When choosing an MPI provider, the mutual exclusivity of
494494
the ``mpi`` metapackage allows picking between mpi providers by installing an mpi provider, e.g.
@@ -580,7 +580,7 @@ Remove the ``if mpi...`` condition if all variants should create a strict runtim
580580
chosen at build time (i.e. if the nompi build cannot be run against the mpich build).
581581

582582
Complete example
583-
""""""""""""""""
583+
^^^^^^^^^^^^^^^^
584584

585585
Combining all of the above, here is a complete recipe, with:
586586

@@ -660,7 +660,7 @@ mpi-metapackage exclusivity allows ``mpi_*`` to resolve the same as ``mpi_{{ mpi
660660
if ``{{ mpi }}`` is also a direct dependency, though it's probably nicer to be explicit.
661661

662662
Just mpi example
663-
""""""""""""""""
663+
^^^^^^^^^^^^^^^^
664664

665665
Without a preferred ``nompi`` variant, recipes that require mpi are much simpler. This is all that is needed:
666666

0 commit comments

Comments
 (0)