Skip to content
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 --use-channeldata arg which determines if channeldata is used to find run_exports #3621

Merged
merged 2 commits into from
Jul 22, 2019

Conversation

jjhelmus
Copy link
Contributor

Add a --use-channeldata argument which determines if channeldata is used to determine run_exports when rendering (and builds) a recipe. The default is False which will use run_export information from the packages directly.

jjhelmus added 2 commits July 19, 2019 14:02
The --use-channeldata argument can be used to select if rendering uses
channeldata.json to determine run_exports. The default or when
channeldata is not available is to download packages to determine this
information.
Do not use channeldata to determine run_exports unless the
--use-channeldata argument is passed on the command line or the
use_channeldata configuration option is suplied.

Additionally only packages which do not have channeldata are download if
channeldata is used.  Previously all packages would be downloaded if any
packages was missing run_export information in channeldata.
Copy link
Contributor

@msarahan msarahan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@github-actions
Copy link

Hi there, thank you for your contribution!

This pull request has been automatically locked because it has not had recent activity after being closed.

Please open a new issue or pull request if needed.

Thanks!

@github-actions github-actions bot added the locked [bot] locked due to inactivity label Mar 25, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 25, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked [bot] locked due to inactivity
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants