On Thu, Sep 20, 2012 at 2:16 PM, Greg Von Kuster <g...@bx.psu.edu> wrote:
> Hi Peter,
> On Sep 20, 2012, at 5:53 AM, Peter Cock wrote:
>> Hi all,
>> I'd like to check (before I try this), if is this expected to work or not?
>> For the normal tool wrappers, is it possible to rename the XML
>> file (but leave the tool ID inside the XML file unchanged), and
>> have this *just work* (TM) when automatically updated via the
>> ToolShed?
> Yes, this is possible (and works), but make sure to do the following:
> 1. Do not change the tool ID string nor the tool version string,
> just rename the tool config.
> 2. Make sure to upload the change as a tarball, and keep the
> following select list checked as "Yes".  This means that you
> need to have everything in your tarball that you want to keep.
> The old tool config will be eliminated and the new, renamed
> one will replace it.  Since the tool id and version remain the
> same, the "valid / installable" changeset revision will be reset
> to the new tip.

OK. What would happen if I did the rename and increased
the version number in one step (which seems the most
common situation)?

>> Similarly, for the new 'blast_datatypes' Tool Shed entry, can
>> I rename xml.py which defines the file format(s) to something
>> like ncbi_blast.py (and update the datatypes_conf.xml
>> ToolShed file to match)? My desire here is partly to avoid
>> the current namespace clash with galaxy.datatypes.xml
>> but also that I intend this to include other non-XML BLAST
>> formats as well (e.g. BLAST database).
> This change should pose no problems.  As you state, just
> make sure to change the repository's datatypes_conf.xml
> file accordingly.

Excellent - I'll try to do that rename operation today for the
BLAST datatypes.

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:


Reply via email to