Skip to content

Commit 19a2c0c

Browse files
jaimergpdhirschfeld
andcommitted
Add extra context around required pip flags
Co-authored-by: dhirschfeld <[email protected]>
1 parent 6cbd394 commit 19a2c0c

File tree

1 file changed

+10
-3
lines changed

1 file changed

+10
-3
lines changed

docs/maintainer/adding_pkgs.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -389,9 +389,16 @@ requirements:
389389
- pip
390390
```
391391

392-
These options should be used to ensure a clean installation of the package without its
393-
dependencies. This helps make sure that we're only including this package,
394-
and not accidentally bringing any dependencies along into the conda package.
392+
`conda-forge` configures `pip` to ensure a clean installation of the package
393+
without its dependencies so no extra flags are required to be passed. This
394+
helps make sure that we're only including this package, and not accidentally
395+
bringing any dependencies along into the conda package.
396+
397+
:::warning
398+
If your package uses `outputs` you may have to manually specify the flags
399+
`--no-deps --no-build-isolation` due to a bug in `conda-build`. See
400+
[conda-build#3993](https://github.com/conda/conda-build/issues/3993).
401+
:::
395402

396403
Usually pure-Python packages only require `python`, `setuptools` and `pip`
397404
as `host` requirements; the real package dependencies are only

0 commit comments

Comments
 (0)