Closed pvalena closed 1 year ago
We have agreed on the internal meeting, that ruby-3.2 container will not be part of sclorg/s2i-ruby-container. We will skip it and later on add ruby-3.3.
@jackorp Am I right?
Yep, no Ruby 3.2 for sclorg/s2i-ruby-container.
For Fedora IIRC the comment was that if the community really wants it, we can merge, build and it's on a self-support basis. As in, you find a bug, you fix it yourself.
This is just for testing purposes... can I push it to 3.2-experimental
branch or similar?
Related issue: https://github.com/sclorg/s2i-ruby-container/issues/461.
This is just for testing purposes... can I push it to
3.2-experimental
branch or similar?
Will it bring you any benefits to move this from your fork to non-main sclorg branch?
This is just for testing purposes... can I push it to
3.2-experimental
branch or similar?Will it bring you any benefits to move this from your fork to non-main sclorg branch?
Just for transparency. In case someone wants to experiment with it as well.
We have agreed on the internal meeting, that ruby-3.2 container will not be part of sclorg/s2i-ruby-container. We will skip it and later on add ruby-3.3.
@jackorp Am I right?
I just want to check that everything still works with Ruby 3.2
even if it's not packaged. E.g. using Ruby from my COPR: https://copr.fedorainfracloud.org/coprs/pvalena/ruby/
Btw. there's like 20 other random branches, so it probably doesn't matter...
Btw. there's like 20 other random branches, so it probably doesn't matter...
That is true, but they are kind of polluting the repository and it would be difficult to get rid of them and make sure not to delete someone's work-in-progress. I would therefore suggest primarily using forks in the future. However, your point seem like a valid one to me.
Thanks for the comments!
And here's the built image, in case someone's interested: quay.io/s2i-ruby/fedora:3.2-experimental
In Fedora container:
Build log: https://gist.github.com/pvalena/4caf0873c714acc8e2b14dc6d88de315