Skip to content

Conversation

@lvkessel
Copy link

In the manwhile, we start to depend on the modified version of ELSEPA taking the ELSEPA_DATA environment variable.

The new elscata() function now takes paths to the elscata binary and the data directory. They default to /opt/elsepa and /opt/elsepa/data, respectively. Is this a sensible default? Any alternative ideas for making the installation procedure more foolproof?

Luc van Kessel added 2 commits November 23, 2017 16:20
Uses a temporary working directory for elsepa, making it possible to run multiple instances in parallel. Does require the modified version (github.com/eScatter/elsepa) of elsepa, to take the ELSEPA_DATA environment variable.
@jhidding
Copy link
Contributor

Consider installing Elsepa in ~/.local, or /usr/local, and have Python figure out where it is by searching $PATH (using shutil.which). Another option is having the user setting ELSEPA_DATA in the bashrc or setting it up in a virtual env.

Luc van Kessel added 2 commits November 24, 2017 10:53
@lvkessel
Copy link
Author

Good points! I added an "install" target to the ELSEPA makefile, which installs to /usr/local by default and asks the user to set the ELSEPA_DATA environment variable.

Pyelsepa now uses PATH and ELSEPA_DATA by default, but this can be overridden.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants