Let conda-lock produce both unified and platform-specific lockfiles #123
Conversation
Passing `--kind=lock` flag to produce unified 'conda-lock.yml' file, in addition to the current 'conda-linux-64.lock' file.
|
|
| - name: Run conda-lock | ||
| run: | | ||
| conda-lock lock --mamba --kind explicit --file environment.yml --platform linux-64 | ||
| conda-lock lock --mamba --kind lock --kind explicit --file environment.yml --platform linux-64 |
There was a problem hiding this comment.
@scottyhq, at #122 (comment), you said to use:
conda-lock lock -p linux-64
conda-lock render -k explicit -p linux-64
What's the difference between the lock and render subcommands? Is render just converting an existing 'conda-lock.yml' file to 'conda-linux-64.lock' (and thus preventing differences in versions between the two lockfiles)?
There was a problem hiding this comment.
yep! that's my understanding. basically conda-lock.yml is the single source of truth that you should be able to render different formats for various tools: https://conda.github.io/conda-lock/output/
There was a problem hiding this comment.
Ok, have split it into two separate lock and render commands. Will need to merge this into main branch first and then ask the bot to generate the lockfiles in a follow-up PR.
Separate the two steps so that the unified lockfile is the source that is used to produce the platform-specific lockfiles later.
Co-authored-by: Scott Henderson <[email protected]>
Running
conda-lock lock --kind=lockto produce a unified 'conda-lock.yml' file, and thenconda-lock renderto get a platform-specific 'conda-linux-64.lock' file as before.Fixes #122.