We, actually have problems with installation of some tools using the
galaxy web interface or the API throught the script
When a tool has a package dependency, the dependency is installed, but
the env.sh of this dependency is not sourced at the end of its
installation and before the installation of the parent tool.
So the dependency is installed, but the parent tool installation failed
because it needs the env.sh of the depency sourced.
For example for GATK : When we install GATK, it looks up for R, which is
installed correctly but its path is not sourced so GATK installation
Any idea ? Do we have a problem in our configuration or it's a known
Thanks in Advance for your response.
Mikael & Françoise