Skip to content

Commit

Permalink
Fix some links and accompanying text
Browse files Browse the repository at this point in the history
Co-authored-by: jaimergp <jaimergp@users.noreply.github.com>
  • Loading branch information
h-vetinari and jaimergp authored Jun 22, 2023
1 parent fece605 commit 1922e90
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions src/maintainer/infrastructure.rst
Original file line number Diff line number Diff line change
Expand Up @@ -285,7 +285,7 @@ in all of our CI builds to build essentially all artefacts published by conda-fo

This compiler infrastructure has a critical role beyond building everything, which
is to ensure that packages stay compatible with each other. This is due to how compiled
packages have a so-called `Application Binary Interface <https://pypackaging-native.github.io/background/binary_interface>`_
packages have a so-called `Application Binary Interface <https://pypackaging-native.github.io/background/binary_interface>`__
(ABI), and how changes in the compiler infrastructure may break this ABI, leading
to crashes, miscalculations etc. Generally speaking, using a consistent compiler
version greatly reduces the risk of ABI breaks.
Expand Down Expand Up @@ -339,7 +339,7 @@ For such ABI-compatible upgrades, similar but looser principles apply:

Despite the lack of explicit support, we try to keep the compilers in their various versions
working also outside of conda-forge, and even provide an easy way to install them
(through the `compilers <https://github.com/conda-forge/compilers-feedstock>`_ feedstock).
(through the `compilers feedstock <https://github.com/conda-forge/compilers-feedstock>`__).

More specifically, each compiler uses an _activation_ package that makes the difference
between it being merely present in a build environment, and it being used by default.
Expand Down Expand Up @@ -407,8 +407,8 @@ and mention any such notices in the discussion about the upgrade.

For Windows, we stay on older compilers for longer, because using a newer toolchain
would force everyone wanting to locally develop with conda-forge artefacts to use
a toolchain that's at least as new. A more in-depth explanation can be found
`here <https://github.com/conda-forge/conda-forge.github.io/issues/1732>`_.
a toolchain that's at least as new. You can find more details about this topic in this
`issue about updating to the vc142 toolchain <https://github.com/conda-forge/conda-forge.github.io/issues/1732>`_.

CentOS ``sysroot`` for ``linux-*`` Platforms
---------------------------------------------
Expand Down

0 comments on commit 1922e90

Please sign in to comment.