-
Notifications
You must be signed in to change notification settings - Fork 493
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
Use version range instead of OSEM_RUBY_VERSION. #2646
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2646 +/- ##
==========================================
+ Coverage 80.5% 82.15% +1.64%
==========================================
Files 146 146
Lines 4832 4780 -52
==========================================
+ Hits 3890 3927 +37
+ Misses 942 853 -89
Continue to review full report at Codecov.
|
its work for me
|
We don't really need 2.5, so this would limit us too much. Sorry, thanks anyway 💐 |
The point is to document what you do need. |
Targets: docker run --rm \ registry.opensuse.org/opensuse/infrastructure/osem/containers/osem/base \ ruby --version See also: - openSUSE#2646 - openSUSE#2680
Checklist
master
branch.Short description of what this resolves
In order to accommodate variation in the version of Ruby across environments, the Gemfile is currently runtime-configurable via
OSEM_RUBY_VERSION
:osem/Gemfile
Line 5 in e6f3aa5
This mechanism is incompatible with typical Docker environments since, by design, the runtime configuration has no effect on builds:
Furthermore, that it's apparently become routine to circumvent the Ruby specification raises the question of why that constraint exists at all. If users are typically expected to set
OSEM_RUBY_VERSION
, what purpose does the Ruby specification serve?Changes proposed in this pull request
As with the other dependencies, specify a range of compatible versions. I've guessed at a conservative starting point: