{"action":"created","issue":{"url":"https://api.github.com/repos/bioconda/bioconda-recipes/issues/393","labels_url":"https://api.github.com/repos/bioconda/bioconda-recipes/issues/393/labels{/name}","comments_url":"https://api.github.com/repos/bioconda/bioconda-recipes/issues/393/comments","events_url":"https://api.github.com/repos/bioconda/bioconda-recipes/issues/393/events","html_url":"https://github.com/bioconda/bioconda-recipes/pull/393","id":120927421,"number":393,"title":"diamond 0.7.10","user":{"login":"yesimon","id":601839,"avatar_url":"https://avatars.githubusercontent.com/u/601839?v=3","gravatar_id":"","url":"https://api.github.com/users/yesimon","html_url":"https://github.com/yesimon","followers_url":"https://api.github.com/users/yesimon/followers","following_url":"https://api.github.com/users/yesimon/following{/other_user}","gists_url":"https://api.github.com/users/yesimon/gists{/gist_id}","starred_url":"https://api.github.com/users/yesimon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/yesimon/subscriptions","organizations_url":"https://api.github.com/users/yesimon/orgs","repos_url":"https://api.github.com/users/yesimon/repos","events_url":"https://api.github.com/users/yesimon/events{/privacy}","received_events_url":"https://api.github.com/users/yesimon/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2015-12-08T04:22:23Z","updated_at":"2015-12-11T19:37:55Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/bioconda/bioconda-recipes/pulls/393","html_url":"https://github.com/bioconda/bioconda-recipes/pull/393","diff_url":"https://github.com/bioconda/bioconda-recipes/pull/393.diff","patch_url":"https://github.com/bioconda/bioconda-recipes/pull/393.patch"},"body":"Accelerated BLAST compatible local sequence aligner.\r\n\r\nIncludes patch from https://github.com/bbuchfink/diamond/issues/24.\r\n\r\nAlso includes a general workaround for GCC 5 dual ABI incompatibility. The situation is not great since the gcc-5/clang incompatibility bug has not been solved yet, but I'm hoping that the anaconda team will do a full rebuild of C++ pkgs with GCC 5 dual ABI and assume everything in conda is gcc."},"comment":{"url":"https://api.github.com/repos/bioconda/bioconda-recipes/issues/comments/164029814","html_url":"https://github.com/bioconda/bioconda-recipes/pull/393#issuecomment-164029814","issue_url":"https://api.github.com/repos/bioconda/bioconda-recipes/issues/393","id":164029814,"user":{"login":"yesimon","id":601839,"avatar_url":"https://avatars.githubusercontent.com/u/601839?v=3","gravatar_id":"","url":"https://api.github.com/users/yesimon","html_url":"https://github.com/yesimon","followers_url":"https://api.github.com/users/yesimon/followers","following_url":"https://api.github.com/users/yesimon/following{/other_user}","gists_url":"https://api.github.com/users/yesimon/gists{/gist_id}","starred_url":"https://api.github.com/users/yesimon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/yesimon/subscriptions","organizations_url":"https://api.github.com/users/yesimon/orgs","repos_url":"https://api.github.com/users/yesimon/repos","events_url":"https://api.github.com/users/yesimon/events{/privacy}","received_events_url":"https://api.github.com/users/yesimon/received_events","type":"User","site_admin":false},"created_at":"2015-12-11T19:37:55Z","updated_at":"2015-12-11T19:37:55Z","body":"If we pin on a conda `gcc` version, this would make local builds more consistent because we would know the gcc version. On the other hand I've always viewed local builds as analogous to the `--build-from-source` option on homebrew, which is to compile from source locally either for the sake of optimization or compatibility with the system. In this case it would probably be desired for the user to be able to use their own compiler, whether it is a different GCC version or clang or whatever.\r\n\r\nThe reason why I view it that way is because the binary packages are really meant for maximum portability - they should install on any OS with the correct platform and are the easiest to use for end users. Pinning to gcc doesn't really affect the consistency of the binary package build process because it's already happening on a fixed compiler and container (specified in Dockerfile) and fixed host platform (Travis). "}}