Skip to content
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

do not set frozen-string-literal env var for ruby 2.2 [changelog skip] #2066

Merged
merged 1 commit into from Nov 3, 2019
Merged

do not set frozen-string-literal env var for ruby 2.2 [changelog skip] #2066

merged 1 commit into from Nov 3, 2019

Conversation

kmossco
Copy link
Contributor

@kmossco kmossco commented Nov 2, 2019

Description

Closes: #2064

Ruby 2.2 doesn't accept this literal with a warning in the Travis build:

ruby: warning: unknown argument for --enable: `frozen-string-literal'

Ideally I'd prefer to have this as a global variable and add an exception for Ruby 2.2 in case there are more versions added later on. But looking at the docs doesn't seem like there is a way to do that: https://docs.travis-ci.com/user/environment-variables/#global-variables.

@kmossco kmossco changed the title set frozen-string-literal env var on each build instead of globally [changelog skip] do not set frozen-string-literal env var for ruby 2.2 [changelog skip] Nov 2, 2019
@nateberkopec nateberkopec merged commit 3203159 into puma:master Nov 3, 2019
@kmossco kmossco deleted the bv/do_not_use_global_literal_env_var branch November 3, 2019 22:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

--enable-frozen-string-literal set incorrectly in tests
2 participants