MNT: set MINIFORGE_HOME: C:\Miniforge

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-webservice.

I've started rerendering the recipe as instructed in #20.

If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!

Here's a checklist to do before merging.

• Bump the build number if needed

Fixes #20

---

From @jaimergp:

Hey, we are optimizing the provisioning overheads on Windows (download Miniforge, install dependencies, etc), and we will change the default installation path from C:\Miniforge to D:\Miniforge. This will reduce the installation times significantly. We are submitting this PR here because this feedstock was redefining CONDA_BLD_PATH to the C: drive. In that case, we do not want to move Miniforge to C:; we want both paths to be in the same drive! This should not create new builds, just protect against the upcoming change in conda-smithy, once rerendered.

More information at conda-forge/conda-smithy#2076

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

[jan-janssen]

Looks good to me

[moritzwilksch]

we still have to bump the build no right?

[jaimergp]

Not really, the packages won't be uploaded if they already exist. This is not changing how the packages are built yet, only defending against the upcoming conda-smithy release. You can merge with a [ci skip] commit too and that would be enough.

[jaimergp]

10 days have passed to I'm merging this with [ci skip] to unblock conda-forge/conda-smithy#2076. Thanks!