Implementation of --try-dependency and --try-builddependency

[mboisson]

The goal of this PR is to let someone easily modify existing dependencies or add new ones without having to rewrite an EasyConfig. The use-case that triggered this is being able to recompile CUDA software with different versions of CUDA.

It works like this:

eb AutoDock-GPU-1.5.3-GCC-10.3.0-CUDA-11.3.1.eb --try-dependency="('CUDA','11.4')" 

Multiple dependencies can be updated by repeating the flag:

eb AutoDock-GPU-1.5.3-GCC-10.3.0-CUDA-11.3.1.eb --try-dependency="('CUDA','11.4')" --try-dependency="('CMake', '3.23.1')"

If a dependency with a matching name is found (i.e. CUDA 11.3.1) then the dependency is updated with the value specified. If no dependency with a matching name is found, then the dependency is added to the list.

[mboisson]

Hum, I don't understand why there's already a test with dependencies and builddependencies when no options for --try-dependencies and --try-builddependencies existed before... 🤔

[boegel]

Hum, I don't understand why there's already a test with dependencies and builddependencies when no options for --try-dependencies and --try-builddependencies existed before... 🤔

Maybe via --try-amend?

[mboisson]

maybe. I renamed the options to dependency rather than dependencies to work around the test. They can only take a single dependency at a time anyway...

[ocaisa]

Does this act recursively with --robot?

[mboisson]

Does this act recursively with --robot?

no idea, I don't use --robot and I don't know how it works :)

[boegelbot]

@mboisson: Tests failed in GitHub Actions, see https://github.com/easybuilders/easybuild-framework/actions/runs/3283047730
Output from first failing test suite run:

ERROR: test_get_source_tarball_from_git (test.framework.filetools.FileToolsTest)
Test get_source_tarball_from_git function.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/tmp/runner/f3e2fe88f7c0b3ab8fa6f54f3bdaf89e5b2a37af/lib/python2.7/site-packages/test/framework/filetools.py", line 2891, in test_get_source_tarball_from_git
    raise err
EasyBuildError: 'cmd "git clone --depth 1 --branch tag_for_tests https://github.com/easybuilders/testrepository.git" exited with exit code 128 and output:\nCloning into \'testrepository\'...\nerror: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500\nfatal: expected flush after ref listing\n'

----------------------------------------------------------------------
Ran 819 tests in 1077.411s

FAILED (errors=1)
ERROR: Not all tests were successful.

bleep, bloop, I'm just a bot (boegelbot v20200716.01)
Please talk to my owner @boegel if you notice you me acting stupid),
or submit a pull request to https://github.com/boegel/boegelbot fix the problem.

[mboisson]

Does this act recursively with --robot?

no idea, I don't use --robot and I don't know how it works :)

I guess a partial answer to that is: if --robot will tweak dependencies by calling tweak_one down the line, then yes. Note that tweak_one does not seem to be triggered when updating both toolchains and dependency unless you add --disable-map-toolchain (which we almost always do because we almost always run into issues updating toolchains without --disable-map-toolchain)