Re: [galaxy-dev] Building tool dependencies

>> Please keep all replies on the list by using "reply all" >> in your mail client. To manage your subscriptions to this >> and other Galaxy lists, please use the interface at: >> https://lists.galaxyproject.org/ >> >> To s

[galaxy-dev] July Galactic News: GCC2016, GCC2017(!), Admin/Dev Trainings, GAMe 2017!

Hello all, Some highlights from the *July Galaxy News :* - GCC2016 is done! and slides and posters are now online (and video and training materials are c

Re: [galaxy-dev] Using operations on multiple datasets

Hi, Am 05.07.2016 um 23:18 schrieb D K: > Sorry for the crosspost to Biostars, but I didn't get a response, so I > thought I'd post here: > > I just noticed that Galaxy allows creation of lists of datasets by clicking > on the "Operations on multiple datasets" in the history panel. How does one >

[galaxy-dev] Using operations on multiple datasets

Sorry for the crosspost to Biostars, but I didn't get a response, so I thought I'd post here: I just noticed that Galaxy allows creation of lists of datasets by clicking on the "Operations on multiple datasets" in the history panel. How does one use this with a custom tool (e.g. what does one put

Re: [galaxy-dev] Building tool dependencies

Hello Matthias From what I've seen there are a number of different recipes used for installing Python packages via the toolshed; the approach you're using seems to be pretty common. In these cases the usual 'shell_command' seems to be: python setup.py install --install-lib $INSTALL_DIR/lib/p

Re: [galaxy-dev] Building tool dependencies

Actually, for recent Galaxy, I'd recommend making a conda recipe for UMI-tools and contributing it to bioconda: https://bioconda.github.io/ Then your tool can just depend on this and the conda dependency resolver (default in Galaxy since 16.01) can find it. Others can comment on the recent work o