Feature request: show rendered run dependencies

[minrk]

This is a feature request for easier auditing/debugging, especially on CI.

I've made some mistakes over the years in packages that resulted in the wrong runtime dependencies, for example:

• assuming deps use run_exports
• unusual results from using the wrong one of pin_run_as_build or pin_subpackage
• pinning build but not version overrides version pinning on conda_build_config (e.g. hdf5 * mpi_*)

These are all my mistakes (to varying degrees), but result in successfully built and tested packages that don't have the dependencies I expect or intend. Often these mistakes don't turn up until much later when a dependency package is updated. I'd have an easier time catching these if I could see the resulting dependencies of the recipe.

One simple version is to explicitly do conda render in conda-forge CI, but it might be nice to include some or all of this in conda-build output by default, particularly requirements.run and build.run_exports, which cannot currently be tested properly.

[msarahan]

Sure, that seems like totally reasonable output after the rendering phase completes. A PR would be welcome, and otherwise we'll try to work it in.

[marcelotrevisani]

I think that is nice indeed
Should we add an option like conda build . --verbose and it will show those extra info ?

[msarahan]

I'd be fine with this being new default behavior, and having a flag to squelch it if so desired.

[minrk]

I'll definitely do this eventually if nobody else gets to it, but I'd love to be beaten to the punch since I'm currently half-time on parental leave and falling further behind every week.

[wolfv]

we have something like this in boa now -- you can check the screencast in the readme. github.com/thesnakepit/boa

[github-actions]

Hi there, thank you for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.

If you would like this issue to remain open please:

1. Verify that you can still reproduce the issue at hand
2. Comment that the issue is still reproducible and include:
   - What OS and version you reproduced the issue on
   - What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!

[jaimergp]

Reopening for upcoming PR addressing this