-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide GNU coreutils in the runtime #70
Conversation
They're provided in our other runtimes (almost by happenstance, as part of the underlying OS image) and having them available in all runtimes makes it much easier to write portable programs without having to deal with GNU vs. BSD differences. Note that typically GNU coreutils would already be available in the Conda runtime on Linux (via the host system), but not the Conda runtime on macOS (unless installed separately, e.g. via Homebrew). So explicitly including GNU coreutils here increases consistency, isolation, and portability of the runtime. Related-to: <nextstrain/ingest#41>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Easy win!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
go gnu or go home
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
I'm not super confident this doesn't break stuff since the pathogen-repo-ci is all "passing" but really doing nothing (c.f. nextstrain/.github#93). So I may address that first. |
Pathogens generally aren't yet ready for the new behaviour beyond v0. Related-to: <nextstrain/.github#93>
The GNU coreutils `sha256sum` is much faster than the custom Python implementation in this repo. We no longer have to worry about portability since GN coreutils has been added to our conda runtime.¹ ¹ <nextstrain/conda-base#70>
They're provided in our other runtimes (almost by happenstance, as part of the underlying OS image) and having them available in all runtimes makes it much easier to write portable programs without having to deal with GNU vs. BSD differences.
Note that typically GNU coreutils would already be available in the Conda runtime on Linux (via the host system), but not the Conda runtime on macOS (unless installed separately, e.g. via Homebrew). So explicitly including GNU coreutils here increases consistency, isolation, and portability of the runtime.
Related-to: nextstrain/ingest#41
Checklist