weixin_39958911
weixin_39958911
2020-12-30 06:27

Trinity package issues

We have an older version of trinity - 2011_11_26, which I believe is overriding the default latest versions in the 2.* series based on trinity version numbering. We need to figure out a new numbering for one-offs, perhaps something like date.2011.11.26, which should work nicely without resorting to an epoch change.

Secondly I believe the OS X version of trinity in the 2.* series is outright broken due to not actually building the core binaries and these packages should be scrubbed from the conda channel. To remedy this I've managed to build a clang only package in the yesimon channel, but with no OpenMP speedups via Parafly because it would be non-native.

该提问来源于开源项目:bioconda/bioconda-recipes

  • 点赞
  • 写回答
  • 关注问题
  • 收藏
  • 复制链接分享
  • 邀请回答

5条回答

  • weixin_39541600 weixin_39541600 4月前

    The "date." prefix sounds good, and the ordering checks out OK via conda/conda/version.py. It's in PR #1315.

    w/r/t the 2.* version on OSX: builds for OSX are currently skipped. If you can alter the current recipe to add your clang-only build for OSX, it would be better than having no Mac builds. If we can preserve the current linux build with OpenMP, we should.

    Paging , since you've worked on the recipe for the 2.* version.

    点赞 评论 复制链接分享
  • weixin_39559369 weixin_39559369 4月前

    It looks good! I don't have an OSX machine to test, so I totally trust you!

    点赞 评论 复制链接分享
  • weixin_39564036 weixin_39564036 4月前

    I think this works fine now, can this be closed?

    点赞 评论 复制链接分享
  • weixin_39559369 weixin_39559369 4月前

    Yes! (for me at least)

    点赞 评论 复制链接分享
  • weixin_39564036 weixin_39564036 4月前

    or can you close this issue?

    点赞 评论 复制链接分享

相关推荐