-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
On master, drop Ubuntu 16.04 "Xenial" LTS and Debian 9 "stretch" #536
On master, drop Ubuntu 16.04 "Xenial" LTS and Debian 9 "stretch" #536
Conversation
Should I drop Xenial and stretch from the build scripts and from CMakeLists.txt in the same PR? I suppose I should. |
Thanks, @nabaco . Unfortunately, I had added 4 more commits on my local machine last night, and another one this morning. Hopefully it's not too much trouble to review those too? |
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'd prefer we change the scripts back to using /bin/bash
instead of using /usr/bin/env bash
; but I'm not going to block. See my comment on the one case for more info/discussion.
@@ -1,4 +1,4 @@ | |||
#!/bin/bash | |||
#!/usr/bin/env bash |
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.
/bin/bash
is actually guaranteed to be there per Linux Standard Base.
/usr/bin/env
is not.
There's various arguments either way for most things, and most scripts engines it can make sense. However, /bin/bash
and /bin/sh
are two that have to be around for a basic system to function and can be directly relied upon so they don't make sense to export out to /usr/bin/env
.
$0.02
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.
Hmm. I can look this up later, I suppose. Anyway, thanks for approving the PR
Thank you for submitting a pull request and becoming a contributor to the Vega Strike Core Engine.
Please answer the following:
Code Changes:
Issues:
Purpose: