Remove GHC from Azure images

[jakirkham]

Removes /opt/ghc from the Azure Linux image to free up some space needed by builds that need more room.

cc @isuruf @h-vetinari @pearu

Checklist

• [x] Used a fork of the feedstock to propose changes
• [ ] Bumped the build number (if the version is unchanged)
• [x] Reset the build number to 0 (if the version changed)
• [x] Re-rendered with the latest conda-smithy (Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• [x] Ensured the license file is being packaged.

xref: https://github.com/conda-forge/omniscidb-feedstock/issues/5 xref: https://github.com/conda-forge/faiss-split-feedstock/pull/5

[conda-forge-linter]

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) and found it was in an excellent condition.

[pearu]

@jakirkham thanks for tackling the shortage of disk space issue :)

[jakirkham]

Of course. Thanks for identify the fix! 😄

[isuruf]

This is run inside the docker container, so it's not going to do anything.

[jakirkham]

I followed your previous suggestion ( https://github.com/conda-forge/omniscidb-feedstock/issues/5#issuecomment-638479644 ). What are you suggesting we do instead?

[pearu]

Would rm -rf /opt/ghc be more effective when executing it from ${CONDA_PREFIX}/etc/conda/activate.d/conda-forge-ci-setup-activate.sh?

[jakirkham]

Guessing that will have the same issue. What if we move this to conda-smithy?

[h-vetinari]

Thanks @jakirkham @pearu for tackling this!

@isuruf: This is run inside the docker container, so it's not going to do anything.

We could mount /opt into the container when calling docker run, then the deletion will take effect on the FS as well. Or am I missing something?

[xhochy]

I would have expected to see this PR in smithy where we render the CI templates.

[jakirkham]

Submitted to conda-smithy in PR ( https://github.com/conda-forge/conda-smithy/pull/1345 ).