-
Notifications
You must be signed in to change notification settings - Fork 423
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add an option to export build time dependencies as run_constrained keys and pin strictly #2404
Comments
I was thinking maybe instead of this, we can have a jinja function to help me do this. Something like: package:
name: bob-devel
version: 2018.02.21
requirements:
host:
- curl 7.55.1
run_constrained:
{% for package in packages('host', all=True) %}
- {{ pin_compatible(package, exact=True) }}
{% endfor %} Would render to: package:
name: bob-devel
version: 2018.02.21
requirements:
host:
- ca-certificates 2017.08.26 h1d4fec5_0
- libgcc-ng 7.2.0 h7cc24e2_2
- openssl 1.0.2n hb7f436b_0
- curl 7.55.1 h78862de_4
- libssh2 1.8.0 h9cfc8f7_4
- zlib 1.2.11 ha838bed_2
run_constrained:
- ca-certificates 2017.08.26 h1d4fec5_0
- libgcc-ng 7.2.0 h7cc24e2_2
- openssl 1.0.2n hb7f436b_0
- curl 7.55.1 h78862de_4
- libssh2 1.8.0 h9cfc8f7_4
- zlib 1.2.11 ha838bed_2 |
For that, you'd need to add a new jinja2 function to the context. See these two bits to see how pin_compatible works: https://github.com/conda/conda-build/blob/master/conda_build/jinja_context.py#L192 If you put up a PR, I can help on it. Otherwise, this can go in the backlog, and I'm not sure when I'll get to it. |
Hi there, thank you for your contribution! This issue has been automatically locked because it has not had recent activity after being closed. Please open a new issue if needed. Thanks! |
Following the discussion here: #2001 (comment), I am proposing to add the following feature to conda build.
Currently, there is an option in conda build recipes which allows you to pin all the packages that were used during build time as runtime dependencies. See original pull request here: #741
For example a recipe like:
will have the following
index.json
where
openssl
andzlib
are dependencies ofcurl
. Note that everything is pinned strictly and normally dependencies ofzlib
andopenssl
get pinned strictly too but I did not put it in the example above.I propose a very similar functionality to be added for
run_constrained
keys as well.For example for the following recipe:
we get this:
The text was updated successfully, but these errors were encountered: