Regarding telling the user what happens, I agree this is important. If/when we put this on the web page, we should of course add a link to the shell script (which is well commented and self explanatory) so a user may view it before running.
Second, the script itself should inform the user about what is going on and prompt for [Yes/No]. However, I didn't find a way to do this in the shell script. It seems that the 'read' command is ignored when piping to bash. -- Anders Sat Dec 06 2014 at 9:16:18 PM skrev Johannes Ring <[email protected]>: > On Sat, Dec 6, 2014 at 9:00 PM, Lizao Li <[email protected]> wrote: > > Thanks for offering another way to install FEniCS~ I tried it on the > current > > Archlinux but it did not work: > > > >> Downloading FEniCS Install... > >> Cloning into 'fenics-install'... > >> remote: Counting objects: 125, done. > >> remote: Compressing objects: 100% (124/124), done. > >> remote: Total 125 (delta 69), reused 0 (delta 0) > >> Receiving objects: 100% (125/125), 17.48 KiB | 0 bytes/s, done. > >> Resolving deltas: 100% (69/69), done. > >> Checking connectivity... done. > >> > >> Using HashStack profile fenics.Debian.yaml. > >> > >> Traceback (most recent call last): > >> File "../hashdist/bin/hit", line 9, in <module> > >> from hashdist.cli.main import command_line_entry_point, > >> help_on_exceptions > >> File "/tmp/fenics-install.iKbsxH/hashdist/hashdist/__init__.py", > line 1, > >> in <module> > >> from .spec.hook_api import * > >> File "/tmp/fenics-install.iKbsxH/hashdist/hashdist/spec/__init__.py", > >> line 1, in <module> > >> from .builder import ProfileBuilder > >> File "/tmp/fenics-install.iKbsxH/hashdist/hashdist/spec/builder.py", > >> line 2, in <module> > >> from . import package > >> File "/tmp/fenics-install.iKbsxH/hashdist/hashdist/spec/package.py", > >> line 4, in <module> > >> from .utils import substitute_profile_parameters, to_env_var > >> File "/tmp/fenics-install.iKbsxH/hashdist/hashdist/spec/utils.py", > line > >> 2, in <module> > >> from .exceptions import ProfileError > >> File "/tmp/fenics-install.iKbsxH/hashdist/hashdist/spec/ > exceptions.py", > >> line 1, in <module> > >> from ..formats.marked_yaml import ValidationError > >> File > >> "/tmp/fenics-install.iKbsxH/hashdist/hashdist/formats/marked_yaml.py", > line > >> 17, in <module> > >> from hashdist.deps.yaml.error import Mark > >> File > >> "/tmp/fenics-install.iKbsxH/hashdist/hashdist/deps/yaml/__init__.py", > line > >> 2, in <module> > >> from error import * > >> ImportError: No module named 'error' > > > > > > I do not know of a build-in python module called 'error'. Any idea how to > > fix this? Thanks~ > > Doesn't Arch Linux use python 3 by default? HashDist is written in > python, but currently it doesn't work with python 3. > > Johannes > > > On Sat, Dec 6, 2014 at 1:05 PM, Johannes Ring <[email protected]> wrote: > >> > >> On Sat, Dec 6, 2014 at 6:57 PM, Maximilian Albert > >> <[email protected]> wrote: > >> > 2014-12-06 17:37 GMT+00:00 Anders Logg <[email protected]>: > >> >> > >> >> > >> >> Regarding sudo, everything will be installed in your home directory > (in > >> >> ~/.hashdist) so sudo is not needed. > >> > > >> > > >> > Also, it's probably worth informing the user about this at the start > of > >> > the > >> > installation process. Maybe it's just me, but when I run a script I > like > >> > to > >> > know what it is about to do and where it will put things (just in case > >> > something fails or I want to revert the operation). > >> > >> I agree. > >> > >> Johannes > >> _______________________________________________ > >> fenics mailing list > >> [email protected] > >> http://fenicsproject.org/mailman/listinfo/fenics > > > > > > > > > > -- > > Lizao (Larry) Li > > Univeristy of Minnesota > _______________________________________________ > fenics mailing list > [email protected] > http://fenicsproject.org/mailman/listinfo/fenics >
_______________________________________________ fenics mailing list [email protected] http://fenicsproject.org/mailman/listinfo/fenics
