all the rubies, plus all the arches #134
Conversation
… libffi into build
name pkg_date ruby_version os arch size --- -------- -------------- -- ---- ---- traveling-ruby 20230528 2.6.10 linux arm64 8.5M traveling-ruby 20230528 3.0.4 linux arm64 8.9M traveling-ruby 20230528 3.1.0 linux arm64 8.9M traveling-ruby 20230528 3.1.0-preview1 linux arm64 8.9M traveling-ruby 20230528 3.1.1 linux arm64 8.9M traveling-ruby 20230528 3.1.2 linux arm64 8.9M traveling-ruby 20230528 3.2.2 linux arm64 7.8M traveling-ruby 20230528 3.3.0-preview1 linux arm64 7.8M
3.4.5 / 3.3.7 / 3.2.7
fails to strip on macos 3.4.x ruby versions
3.4.5 not yet avail
|
@FooBarWidget - I guess you aren't interested in the PR! Might as well archive it now fella! From my perspective, I have am pretty much wrapping up a rewrite of the tooling which depended on this package, so my inclination to maintain it will wane, as I am cleaning up my digital garden. It is pretty automated now, and we have much better cross platform support in CI in github actions which pretty much negates the need for cirrus-ci |
|
Hello @YOU54F, I want to let you know that I haven't forgotten your request. I have done my upmost best in the past few months to allocate time, but it just doesn't work out. Between needing to take care of spouse, children, parents, and health issues, I just can't do it. My health is not cooperating and I can't push myself that hard anymore. There are too many obligations and not enough time and health points. I can only advise not to rely too much on me. If you feel strongly about something, go ahead and take matters into your own hands. Fork or start your own project if you want. I'm afraid that for now I have reached the limits of what I can do. |
|
Thanks Hongli, for everything you've done for the project and the ruby community. I can empathise fully on the health situation with family. I hope you can maximise the time to spend with them all. Well if it helps to lift a weight off your mind, you can forget about this pull request, and know that the traveling-ruby torch is being carried on, in an automated fashion, and will hopefully continue on for as long as the operating systems we run on, co-operate! I might make an org for this, and some other ruby packaging tools, I've quite a bit of work across a fair few packagers and it would be a shame to lose it when other intrepid open sorcerers might want to turn their hand to any one of them. We at the pact-foundation, have been eternally grateful for traveling-ruby, it enabled pact-ruby to be used in many different languages, spawned life long friendships, careers, relationships, marriages, jobs in open-source. So thank you from all of the Pact team. Live long and prosper dude ✌🏾 |
|
@YOU54F I've had a lot of value of this PR (we use it for the packaging of our CLI tool for the https://reclaim-the-stack.com project). I didn't fully follow what your intent is now after closing. Do you have an alternative packager in use within Pact which you're considering releasing? In any case. Thanks for your work ❤️ Also thank you @FooBarWidget for initiating this project. Best wishes for your health and family 🙏 |
|
The new home is https://github.com/trubygems/traveling-ruby and the fork has been pulled out of the network for visibility. The rewritten Pact tooling, is in Rust and packaged as a single binary. It doesn't rely on the Pact ruby tooling packaged with Ruby, but does offer downloading those traveling-ruby created packages for legacy compatibility. For those legacy packages, I still rely on the binaries generated as part of this pull request so have done some work to make the CI process as slick as possible for the future, so it can be easily be maintained for a long time. Latest release went out over the weekend - https://github.com/trubygems/traveling-ruby/releases/tag/rel-20251107 I do have plans for improvements to the project, which I will announce soon, but you can rest safe that if you are relying on the project, that existing releases will remain, and you should be able to fork and generate your own binaries easily in github for safe keeping! ( I would consider this a smart idea, if used in production pipelines ) |
7 participants
builds all the rubies for all the things
Fork:- https://github.com/YOU54F/traveling-ruby
background #133 (comment)
Travelling ruby updates for arm64/aarch64
macos x86_64 binaries work as far back at 10.15 Catalina.
10.14 Mojave fails on libgmp