Skip to content

Commit 357dd1c

Browse files
authored
Merge pull request #1393 from hitblunders/patch-3
Improved pinning_deps in maintainer
2 parents 2c6aea1 + 62ac985 commit 357dd1c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/maintainer/pinning_deps.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,14 +11,14 @@ Globally pinned packages
1111
Maintaining a large collection of packages with different requirements poses the danger of producing islands of packages with mutually exclusive dependencies.
1212
Especially widely used libraries with restricted version compatibilities increase the danger of fractioning the package space.
1313
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.
1515

1616
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.
1717
These pinned versions represent the ABIs that conda-forge is currently supporting, with almost all available packages built against that version.
1818

1919
When a rerendering happens, conda-smithy will render the recipe using conda-build and output configuration files for each job and save them in a yaml file in ``.ci_support`` folder. For example, there's an output configuration file for each OS, each python version, etc.
2020

21-
These output configuration files are stripped to options that are used in the build and therefore a change in the config files in ``.ci_support`` folder implies that there needs to be a new build.
21+
These output configuration files are stripped to options that are used in the build and therefore a change in the config files in ``.ci_support`` folder implies that a new build is needed there.
2222

2323
Pinning of packages are handled by the same configuration file and conda-build. This means that packages need not be pinned manually.
2424

0 commit comments

Comments
 (0)