Morning, Martin.
On 06/11/2017 10:56, Martin Raden wrote:
> I finished the Jalview recipe and wrapper for version 1.12.2b2.
>
> https://github.com/bioconda/bioconda-recipes/pull/6605
This is great news !
> The package gets currently build and jalview should be available via
> bioconda within an hour. I will test the commandline-interface somewhen
> this week within our postprocessing pipeline.
I also tested your conda patch over the weekend, and noticed a few issues:
1. Java 9 compatibility (the java command line is different if java 9 is
installed)
2. Memory - I've hacked a script that will max out the memory allocated
to Jalview.
3. Version numbers. Jalview's versioning is 'semi-semantic' - and
traditionally, distributions built via package management systems should
include the package version (so we can distinguish packager specific
issues).
It's trivial to embed the version string, but I'd like to know what the
'recommended' conda approach is here. e.g. can we just have
2.10.2b2-conda${BUILDNUM}
4. Interactive use. You've packaged jalview for headless operation - is
there going to be any interest in having Jalview launch as an
interactive tool ?
I can submit a PR straight away for most of these, but should I do this
via bioconda's repo directly, or via your fork ?
Jim
_______________________________________________
Jalview-dev mailing list
[email protected]
http://www.compbio.dundee.ac.uk/mailman/listinfo/jalview-dev
