You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/maintainer/pinning_deps.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ Globally pinned packages
11
11
Maintaining a large collection of packages with different requirements poses the danger of producing islands of packages with mutually exclusive dependencies.
12
12
Especially widely used libraries with restricted version compatibilities increase the danger of fractioning the package space.
13
13
By fixing crucial libraries to specific dependency version shared by all packages in conda-forge, we avoid fractioning of our packages in incompatible islands.
14
-
The following paragraphs give a short introduction how this global version pinning is realized in conda-forge.
14
+
The following paragraphs give a short introduction about how this global version pinning is realized in conda-forge.
15
15
16
16
The current versions of globally pinned packages are defined in the `conda_build_config.yaml <https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/master/recipe/conda_build_config.yaml>`_ file located in the ``conda-forge-pinning`` feedstock.
17
17
These pinned versions represent the ABIs that conda-forge is currently supporting, with almost all available packages built against that version.
0 commit comments