- Move  IS_WINDOWS
- Remove extra absolutePath implementation

Make minor refactor of `setup` command code

- Set all members of the client main class in the constructor.
- Do not store settings that are not necessary outside the constructor.
- Do not initialize site multiple times in some cases
- Consider --debug and --quiet mutually exclusive
- Print switch information in an ordered way
- Do not run any code until it is known that the call is not being
passed on to the updated haxelib version
  - Fix -cwd not working when redirecting to haxelib version
- Separate command functionality from docs

- Fix specifying a version not working if a development directory is set
- Show an error if a non-existent version is specified instead of
  silently using a different version
- Reset environment variables and current working directory after a run
  so that it is safe to use as a function in a process

- Show error if a non-existent library version is specified with either
  command, instead of silently using a different version, as now with
  the `run` command
- If two versions of the same library are given to path, the error mentions
  them in the order they appeared

- Fix minor issue with alphabetical ordering
  - Before, they were sorted by `name:` instead of `name`, so for
    example `flixel` came after `flixel-addons`, which was incorrect
- Do not list invalid versions

Remove no longer relevant TODO messages

- Check for hashlink c target when searching hxml for dependencies
- Fix installing from `haxelib.json` with `--skip-dependencies` doing
  nothing
  - Previously, installing from a `haxelib.json` file was seen as
    installing dependencies, so with `--skip-dependencies` the command
    would do nothing. Now, with the flag, the libraries in the file are
    not skipped, however their dependencies still are.
- Don't update vcs version if it is not set as current version HaxeFoundation#364
- Decouple cli from installation code
- Disallow setting invalid library versions with `set`

- Fix error when installing from hxml due to capitalisation

- Use two dashes for `--notimeout` and `--cwd`
- Update information on run version resolution

- Fix issue where it was possible to remove a git/hg version even if a
development path was set within it

- Don't show updated message if vcs dependency was already up to date
- Clean up debug logs of git/hg output

To achieve separation of the haxelib cli from the general code that can
be reused.

Versions prior to haxe 4 don't recognise `--version` and print their
version to stderr instead of stdout

Addresses HaxeFoundation#529

This way, list shows the correct version of the name, and path falls
back to the correct version when no haxelib.json is found.

The "correct" version is the way the name in haxelib.json is
capitalized, or if no such file exists it is the way the parameter to
the `dev`/`git`/`hg` command was capitalized. Additionally, if
the parameter is an alias, then it is used instead as well.

It is updated everytime a version is set as current. However, officially
released library version names are preferred over the capitalization of
`dev`, `git`, or `hg` versions.

For example, after:
`haxelib dev LIBRARY <path>`
`haxelib install library 1.0.0`

If `library` is the version in `haxelib.json`, then that is preferred
over `LIBRARY` after we install from the server.

Throw error in `path` command when two versions of the same lib are
queried even if the two versions are capitalized differently.
- e.g. `LiBrArY:1.2.0` and `library:1.3.0`

Ensure that haxelib run sets HAXELIB_RUN_NAME to name field in
`haxelib.json`.

Ignore capitalized directories in `list`.

Also HaxeFoundation#465 and HaxeFoundation#503

- Ensure haxelib is case insensitive for library names
- Ensure haxelib keeps track of correct name capitalization for `list`
command
- Ensure haxelib.json name is preferred with git/hg/dev, unless an alias
is given.
- If there is no haxelib.json, ensure that the last name the user used
is shown
- Ensure running aliased libraries works correctly

Also test HaxeFoundation#357

For removing specific versions

- HaxeFoundation#364
- HaxeFoundation#526
- Ensure `list` doesn't break with invalid directories in the repository
- Ensure `list` doesn't show invalid versions
- Ensure --skip-dependencies doesn't break installing from haxelib.json
- Ensure --cwd works
- Ensure specifying versions with run, path, and libpath commands works
properly HaxeFoundation#249
- Don't show update message if vcs lib was already up to date
- Ensure order of output of `path` is correct
- Ensure remove can't break dev path set inside git/hg version

For breaking changes such as the library name case insensitivity change

Show warning for every command using the repository if it is out of date

`haxelib path` now repeats the version of the name the user typed in if
the library is not installed, instead of making it lowercase

Show error output in case git commands fail to make stuff like this
easier to debug.

Not initialising the field in the abstract class constructor results in
a compiler error in non nightly builds of haxe

Do not depend on how the system sorts child files/directories

We don't need to sort on Windows as it has a case insensitive file
system, so we won't get clashes.

Generate the regex from TARGETS to avoid repetition

`-D run` requires hashlink library to be installed even for bytecode
compilation.

It is now combined with installFromHaxelib, whose version argument is
now optional.

No need to check if the requested version matches the scope version, as
if that were the case it would have been caught in the check above.

Prevent reinstalling existing libraries

Reverting to previous behaviour