Users will have to load this into their shell by sourcing the file,
either directly (at the command line) or in their .bashrc, like this:
source /path/to/bootstrap/install/run-example-completion.bash
Then tab completion will show the output of --list in run-example.
Note that --list isn't actually entirely well-suited for this, so there
is extra garbage that is offered. A change would be needed to
run-example to give it a mode specifically for completion. This does
work, at present.
This also works for zsh.
This is not required to install GNAT CE, but it is required to run GNAT Studio. Since the goal of bootstrap is to get everything set up for the user, it seems more friendly to go ahead and install libncurses5 at the outset.
Rather than having a growing collection of bootstrap scripts, we provide a single bootstrap script whose behavior is controlled through environment variables.
* Support python 3.7 and install pyzmq
The latter is needed for testing, and was omitted accidentally.
* Add e3-testsuite
Needed for running the Ada tests.
* Rename setenv to printenv
This is done for anod internally and seems much more clear than `setenv` (given that it doesn't actually set anything).
Options to print the environment for the installer are also modified to `--printenv` which is consistent with internal anod.
Clean up the output of install - specifically, have it give a correct set of commands to add to the .profile.
Finally, use the better (safer) syntax for the eval, so the user can get used to it.
Support pre-commit checks used in AdaCore/e3-core
These are a good example of best style practices for python projects. Adding the associated badges to the README (even though it needs to be rewritten) so the commit is complete and consistent.
Documentation of how to set up and run the checks is in CONTRIBUTING.md
Master `anod` script that dispatches to subscripts for action.
Add `paths` module, which group common path-related constants.
Improve anod-devel-setup to use e3 and logging.
