> Another vote for the excellent modules system from us at AgResearch. I think
> it's the only sane way to manage PATH, etc, when you have multiple versions
> of tools installed.
> http://modules.sourceforge.net/
> I know I've said this before here. Tell all your friends. ;-)
Galaxy's dependen
Hi,
We have a local server running Galaxy and a majority of the tools work
correctly (bowtie, BWA, samtools and etc.). I am having issues with some of
the FASTX-Toolkit tools. I am starting Galaxy with an init script on Centos
6 and the tools are in my $PATH and work at the command line, just
> From: galaxy-dev-bounces ... On Behalf Of Adam Brenner
> On our HPC setup, we use the modules system but its the same issue you are
> running into.
Another vote for the excellent modules system from us at AgResearch. I think
it's the only sane way to manage PATH, etc, when you have multiple ve
Ryan,
On our HPC setup, we use the modules system but its the same issue you are
running into.
A number of methods exists for setting up the correct path, for you, I
believe the easiest would be one of the two:
1) In your init script: source (or setup) PATHS as you have them in your
.bash_profi
