Better test it to make sure ;)

Of course, if you really want the use the *.loc file as a static configuration
file which should be updated in sync with the tool code, that might be a
problem...

Peter

On Mon, Apr 7, 2014 at 11:09 PM, Dooley, Damion <damion.doo...@bccdc.ca> wrote:
> Oh, great!  I'd assumed new tool versions would overwrite them so they could 
> implement changes.  But what you say is simpler and more straightforward!
>
> Thanks,
>
> D.
> ________________________________________
> From: Peter Cock [p.j.a.c...@googlemail.com]
> Sent: Monday, April 07, 2014 2:23 PM
> To: Dooley, Damion
> Cc: galaxy-dev@lists.bx.psu.edu
> Subject: Re: [galaxy-dev] Can a tool upload a .loc file that is then reused 
> by subsequent versions of the tool?
>
> Isn't this how *.loc.sample files already work? If there is
> no pre-existing *.loc file, the *.loc.sample file is copied
> to become the initial *.loc file which the local Galaxy
> administrator can update/fill in as needed.
>
> 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/

Reply via email to