Hi all,
Again, this may be me sticking to old pre-tool shed habits - so I'd like
> to hear how other people manage their *.loc files, especially when doing
> hand editing to add entries.
>
I **try** to stick to just editing the *.loc file in tool-data for those
tools that do not have a data manag
Hi Matthias,
I'm getting out of my depth here - but if tool-data/xxx.loc is being ignored,
you may need to enable this by adding the XML data table entries from
the relevant tool_data_table_conf.xml.sample file for tool xxx to
$GALAXY/config/tool_data_table_conf.xml.
At least, that's what I had t
Hi Peter,
then the I need to update all the paths in:
`config/shed_tool_data_table_conf.xml`?
Because currently the $GALAXY/tool-data/*.loc files are ignored in my
instance.
For me it looks like a bug (caused by a misconfiguration?) that there
are all xml files refer to the same loc file.
Personally I tend to work with $GALAXY/tool-data/*.loc (and ignore
the tool shed installed copies in their cryptically named folders) but
this reflects in part the fact that this used to be the only copy of the file,
and that's just what I always did.
If you use a data manager, I don't know which
Dear list,
I still have problems to get my head around tool data. Lets consider
diamond for example (lets ignore data managers for the moment). After
installation it seems that there are two relevant xml files:
- `config/shed_tool_data_table_conf.xml`
-
`tool-data/toolshed.g2.bx.psu.edu/repo
