On Mon, Jul 15, 2013 at 7:27 PM, John Chilton chil...@msi.umn.edu wrote:
One of my goals for the GCC was to sell the idea that tool shed
repositories need to be installable without a database present. I
John, as I've mentioned in the past I'm very strongly in favor of
this. There is
On Tue, Jul 16, 2013 at 1:16 PM, James Taylor ja...@jamestaylor.org wrote:
On Mon, Jul 15, 2013 at 7:27 PM, John Chilton chil...@msi.umn.edu wrote:
One of my goals for the GCC was to sell the idea that tool shed
repositories need to be installable without a database present. I
John, as I've
One of my goals for the GCC was to sell the idea that tool shed
repositories need to be installable without a database present. I
talked with James Taylor and Enis Afgan about this idea briefly and they seemed
to believe this was a good idea - I kept meaning to discuss it with Greg but I
never
This would be different from using the API scripts because there would be
no
API, Galaxy instance, or Galaxy database involved - just the Galaxy code.
If
this was able to split into its own Python library, one could imagine even
allowing something like tsmodule to be installable right from
Hi John,
It's really too bad that we didn't find time to discuss this in person at the
GCC. Until now, I've not heard from anyone that installation from the tool
shed without requiring a Galaxy database is important, so I'm lacking some
context on this (I assume your statement without a
