pyiron/pyiron-installer

pyiron installer based on conda constructor

Installers for pyiron

Download the release:

https://github.com/pyiron/pyiron-installer/releases

Remark

After the installation completed successfully it is necessary to activate the installation:

Windows

Open a command prompt and enter:

activate 

Linux/ MacOS

Open a terminal and enter:

source activate

pyiron-installer's Issues

Automate version number generation

We need to change the version in a few places. Try to automate/ incorporate dependabot?

Add tests for pyiron-installer

At least for Linux it should be possible to automatically install conda from the installer which was created and then run a couple of tests just to see if the typical workflows are working.

Create a conda-forge package for the binary LAMMPS packages

LAMMPS started to publish binaries https://github.com/lammps/lammps/releases - so we could repackage those and release them as conda package. This is not possible via the conda-forge community channel, as they do not allow repackaging existing binaries. We could try to add a windows build for the conda-forge community package, but that is going to be more challenging. The alternative is just refreshing the https://anaconda.org/pyiron/lammps package where es already published binaries for LAMMPS previously. Still unfortunately I forgot how I created those packages - five years to go. But maybe it is possible to find some conda-recipes somewhere.

Synchronise docker-stacks and pyiron-installer

It would be great to use the environments from https://github.com/pyiron/docker-stacks/releases for building the installers using the constructor. The issue is that the environment in the docker-stacks are currently only build for linux.

Use Dependabot to update pyiron-installer

Just like https://github.com/pyiron/docker-stacks relies on https://github.com/dependabot it would be great to use https://github.com/dependabot also in the pyiron-installer repository to get notification when one of the dependencies gets updated. Still it is primarily the pyiron package, which triggers an update for building a new installer. Nevertheless this could also be changed to build a new installer with every pyiron_atomistics release