Hi Nik,

Hi Bjorn,

Thanks for your response. It seems to me that the wrapper version is not
really that useful... the thing that is important is the version of the
underlying tool.

Sure, I agree. But on the other side the user should not care about the version, and is on most cases not interested as long as it works :)
But as pointed out I would also like to shift to a more useful numbering, that the arbitrary one we are using now.

I can certainly update the versions to be the versions of

the tool, if need be.

That will break many thing, if you combining your tools with the toolshed and updates would be more complicated. Don't do that, at least not for tools from the ToolShed. Try to convince the Tool Maintainers.

However, I wasn't aware that you could have multiple

versions of the same tool to choose from. How do I get that to work?

You can simply install multiple versions (revisions) from the same tool from the Tool Shed. For example multimple Blast version.

I tried creating two different XML files with the same tool id, but that
didn't work. And how would I make sure the wrapper scripts pointed to the
correct version... it seems like I would have to tailor each script with an
absolute path to the specific version....?

No you need to have the Tool Shed managing that for you. Each version is a separate tool with the same tool-id. Galaxy keeps track of every dependency of a certain tool. So the same tool with different versions with different dependencies will be working over time.

Please read more about all of that in the galaxy wiki, especially about Tools and the Tool Shed:

https://wiki.galaxyproject.org/ToolShed

Cheers,
Bjoern

- Nik.


On Mon, Jul 7, 2014 at 11:56 PM, Björn Grüning <bjoern.gruening@gmail.com>
wrote:

Hi Nik,

you can hack to tool rendering and omit the version string, but I would
not recommend that. The version will be a selectbox as soon as you have
multiple versions from the same tools installed. This is important for
reproducibility.
The best approach would be to fix the version string. Do you have any
suggestions?
For my wrappers I try to go with that version scheme:
{Tool-Version}.{wrapper-version}.

Cheers,
Bjoern

Am 08.07.2014 08:51, schrieb Nikhil Joshi:

Hi all,

So I am trying to remove the version info (at the top of a tool page)
entirely for all the tools. As I understand, those versions are the
versions of the wrappers and not the tools themselves. Although I could
change that, I would rather just not have the versions on the tool pages
at
all. We currently show all the versions of our tools on our landing page.
Is there any way to remove the version part of the tool title entirely?
I.e., if it originally says "Map with BWA for Illumina (version 1.0.0)", I
just want it to say "Map with BWA for Illumina".

- Nik.



___________________________________________________________
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:
    http://lists.bx.psu.edu/

To search Galaxy mailing lists use the unified search at:
    http://galaxyproject.org/search/mailinglists/