Wolf Vollprecht
Wolf Vollprecht
Thanks for the proposal and the implementation. I like the idea and would be happy to accept a PR :)
I think this is clearly not ready. First, it shoudl probably go behind a feature flag enabled by `conda-forge.yml` file (check how the `{{ BOA }}` thing works. And then,...
OK, I think I missed the bits in the conda-forge-ci-setup feedstock a bit. It would probably be better to instead add `conda_oci_mirror` as a package to conda-forge, and add it...
Hey @magentaqin I'll take this PR over and get it merged! I'll remove some changes from the S3 upload because IMO progress bar shoudl go to a different PR.
As a workaround, in the build, you could copy the files from the prefix to the work dir? E.g ``` cp $PREFIX/licenses/foobar.* $SRC_DIR/licenses/ ```
I would say we don't have concrete plans right now. It would also not be super hard to do. We just have to decide that we want it, I guess.
I think the main design question is whether we want: ``` license_file: source: - my_license.txt recipe_dir: - license.txt prefix: - license-foobar.txt ``` Or whether we go with ``` license_file: -...
I guess I could live with this. In the tests section, we changed the schema a bit to use: ```yaml ... files: source: - myfile.txt - tests/ - some/directory/pattern*.sh recipe:...
I do want to pick this up again, but use `${{ PREFIX }}` in the recipe file and then resolve that at "globbing time". Unfortunately that is a bit more...
This is on macOS?