Hi Dave,
> Björn,
>
> I've uploaded the modified tool_dependencies.xml to devteam's
> package_emboss_5_0_0 repository on the test tool shed, and verified that
> it works. Again, thank you for your contributions.
Great, thanks!
> --Dave B.
>
> On 7/7/13 18:59:57.000, Björn Grüning wrote:
Björn,
I've uploaded the modified tool_dependencies.xml to devteam's
package_emboss_5_0_0 repository on the test tool shed, and verified that
it works. Again, thank you for your contributions.
--Dave B.
On 7/7/13 18:59:57.000, Björn Grüning wrote:
Hi Greg,
bitbucket has a downtime so I
Hello Björn,
Thanks very much for the patch - I've committed alsightly alterered verson of
it in changetset 10204:afec613d77fa which is currently running on the test tool
shed.
Greg Von Kuster
On Jul 7, 2013, at 6:59 PM, Björn Grüning
wrote:
> Hi Greg,
>
> bitbucket has a downtime so I hav
I'll soon be committing a slightly altered version of your patch which includes
a language attribute for the template_command action type.
On Jul 8, 2013, at 10:02 AM, Björn Grüning
wrote:
> Hi James,
>
>> It probably makes sense to specify the template type in this case.
>> Maybe an addition
Hi James,
> It probably makes sense to specify the template type in this case.
> Maybe an additional attribute, language='cheetah' ?
My first suggestion was to reflect the
template engine. I'm fine with both.
> On Sun, Jul 7, 2013 at 1:19 PM, Björn Grüning
> wrote:
> >
> > #if env.get('X
It probably makes sense to specify the template type in this case.
Maybe an additional attribute, language='cheetah' ?
On Sun, Jul 7, 2013 at 1:19 PM, Björn Grüning
wrote:
>
> #if env.get('X11_LIB_DIR', False) and env.get('X11_INCLUDE_DIR', False):
>./configure --prefix=$env.INST
Hi Greg,
bitbucket has a downtime so I have attached a patch. I will create
tomorrow a pull request if I find time.
It will work as described and we have now a new variable (__is64bit__)
that we can use to determine if python is running under 64bit (assuming
that the rest is also 64bit-ish).
Att
Hi Björn,
This is great. A pull request or a patch is fine. Whatever one is most
convenient for you. The code doesn't have to be pretty, just functional. We
can always pretty it up later.
Thanks very much for doing this!
Greg
On Jul 7, 2013, at 1:19 PM, Björn Grüning
wrote:
> Hi Greg,
Hi Greg,
> Hello Björn,
>
> This would be great! I'm not sure about the type attribute - type="cheetah_command" may be ok, but maybe a more generic type like type="template_command" would be better.
> I'm not quite sure, so go with what you feel is best.
I come up with the following:
Hello Björn,
This would be great! I'm not sure about the type attribute - wrote:
> Hi,
>
> I was thinking how to tackle the build failures like the atlas library
> on OS-X or the ones from xlib and ease the writing of the shell_command
> a little bit.
>
> Dave B did some fancy shell scripting
Hi,
I was thinking how to tackle the build failures like the atlas library
on OS-X or the ones from xlib and ease the writing of the shell_command
a little bit.
Dave B did some fancy shell scripting in 'package_emboss_5_0_0' and I
was also sometimes forced to use some bash tricks.
What about to
11 matches
Mail list logo
