Some cookbook entries were failing with an error like this:
```
error: no such subcommand: `config`
```
We can install this subcommand from the bootstrap script, and also
instruct folks in the README to do so manually.
The script shouldn't upgrade a system, period, see my comments. I also
added a cli option to run the bootstrap with an update of the git stuff
and run rustup, plus a help flag and the statusCheck.
These packages are also required to build the C apps in the cookbook and to generate the live ISO image. Tested with a clean install of Ubuntu Server 16.04.4 and Pop!_OS Intel 62.
See https://github.com/redox-os/redox/issues/1052
This is just something fast I threw together to get the general idea across of what might fix the problem. I've not yet had a chance to test this.
macOS again.
Details
- We are using the toolchain compiler and archiver in order
to generate a proper ELF file when building the 'raw-cpuid'
crate C code which is currently being compiled by the macOS
toolchain.
- I added the 'findutils' and 'coreutils' Homebrew/MacPorts
packages to the bootstrap script in order to setup the proper
environment for the cookbook scripts (as the assume GNU tools).
This should be temporary until the cookbook scripts get migrated
to Rust.
On my OS X El Capitan machine `which` returns 1 if it can't find the binary. This kills the bootstrap script at the crucial moment when it detects that something needs to be installed. This change ignores unsuccessful exit codes from `which`. The man page for my `which` speaks of a `-s` switch that could be used instead of the `if [ -z`, but I don't know how portable this is.
This fixes Issue 850.
* update bootstrap.sh script
+ macOS users using MacPorts are now supported (fix issue #720);
+ dependencies for macOS users using brew have been updated;
+ the boot step can now be skipped with the '-d' flag, effectively only installing dependencies
* update summary build instructions in README dependencies step
as these are meant as quick instructions, it's probably better to simply use the bootstrap.sh script available in the repo root folder, using the '-d' flag to just install the dependencies, using whatever package manager is available for the host system, rather than forcing the user to manually install those one by one
