Skip to content

Installer should check for non-conda-forge installed packages #1190

@LourensVeen

Description

@LourensVeen

Is your feature request related to a problem? Please describe.
A mix of conda-forge and non-conda-forge packages in the environment can cause weird and hard-to-debug errors, and it's easy to get into this state if you have miniconda or anaconda.

Describe the solution you'd like
It would be nice if the setup script checked for this if we're in a conda environment, and printed a warning, ideally with a command to reinstall the affected packages from conda-forge.

Describe alternatives you've considered

  • Continue to work with individual users to fix their messed up Conda set-up
  • Tell affected users to just buy a new computer
  • Kindly ask Anaconda Inc. to discontinue their product and tell everyone to switch to miniforge
  • Move to a deserted island somewhere in the South Pacific and start a coconut shell collection

Additional context
Possibly related: gfortran printing clang: error: no input files on macos (not making this up)

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: building/installingIssue relates to the build system and installing from sourcekind: feature requestThe issue requests a feature that AMUSE does not currently have

    Type

    No type

    Projects

    Status

    Feature Request

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions