This would be easy to implement, but could adversely affect reproducibility.  
If a repository containing datatypes always had only a single installable 
revision (i.e., the chagelog tip), then any datatypes defined in an early 
changeset revision that are removed in a later changeset revision would no 
longer be available.

Greg

On Jul 17, 2014, at 1:30 PM, Peter Cock <p.j.a.c...@googlemail.com> wrote:

> On Thu, Jul 17, 2014 at 6:10 PM, Björn Grüning
> <bjoern.gruen...@gmail.com> wrote:
>> 
>> ... but the problem will stay the same ... one [datatype definition] 
>> repository
>> can have multiple versions ...
>> 
> 
> I like your idea that like tool dependency definitions, this should be a 
> special
> repository type on the ToolShed:
> 
> Earlier, Björn Grüning <bjoern.gruen...@gmail.com> wrote:
>> 
>> Imho datatypes should be handled like "Tool dependency definitions".
>> There should be only one "installable revsion".
>> 
> 
> This is something Greg will have to comment on - there may be
> ramifications I'm not seeing.
> 
> Peter
> 
> ___________________________________________________________
> 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/
> 


___________________________________________________________
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/

Reply via email to