Luke T. Shumaker
ad7742856c
libre/ruby: Fuss with metadata
|
vor 2 Monaten | |
|---|---|---|
| .. | ||
| 0001-FSDG-rubygems-Have-default_sources-be-empty.patch | vor 2 Monaten | |
| 0001-Prep-to-use-Parabola-s-patched-ruby-json.patch | vor 2 Monaten | |
| PKGBUILD | vor 2 Monaten | |
| README.md | vor 2 Monaten | |
| build-rebuild-todo-list.sh | vor 2 Monaten | |
README.md
Ruby Packaging
Bootstrap
To transition to a new language version of Ruby like 3.2 to 3.3, the process involves three main phases: initial bootstrapping with non-de-vendored gems, rebuilding a base set of Ruby packages using the de-vendored gems, and finally, a comprehensive rebuild of all existing Ruby-dependent packages in the correct sequence.
bundled gem compatibility
A list of compatible bundled gem versions for packaging can be found at https://stdgems.org. The de-vendored packages should make sure to be compatible to the ruby version.
bootstrap packages
The bootstrapping phase starts with the creation of a minimal set of bootstrap packages, bootstrapped with the non-de-vendored gems. This step aims to establish a foundational Ruby environment that is capable of supporting the compilation and installation of more complex Ruby applications and libraries.
Build the following packages:
- ruby (which includes the ruby-default-gems-bootstrap and ruby-bundled-gems-bootstrap split packages)
Build the following packages in the given order with ruby-default-gems-bootstrap and ruby-bundled-gems-bootstrap installed:
- rubygems
--nocheck - ruby-rake
- ruby-hoe
- ruby-kpeg
- ruby-rdoc
- ruby-irb
- ruby-power_assert
--nocheck - ruby-test-unit
- ruby-webrick
- ruby-erb
--nocheck
base set
Following the initial setup, the next step involves the rebuilding of a specific chain of Ruby packages using the de-vendored packages. This production build should be a de-vendored version of Ruby, intended for deployment. The purpose of this phase is to compile a full base set of Ruby packages that are ready for consumption. This includes key libraries and tools necessary for the broader Ruby ecosystem.
Build the following packages in the given order:
- rubygems
- ruby-rake
- ruby-bundler
- ruby-webrick
- ruby-rake-compiler
- ruby-test-unit-ruby-core
- ruby-erb
- ruby-power_assert
- ruby-test-unit
- ruby-diff-lcs
- ruby-rspec-support
- ruby-rspec-core
- ruby-rspec-expectations
- ruby-rspec-mocks
- ruby-rspec
- ruby-rr
--nocheck - ruby-test-unit-rr
- ruby-rr
- ruby-debug
- ruby-irb
- ruby-minitest
- ruby-hoe
- ruby-kpeg
- ruby-racc
- ruby-rdoc
- ruby-typeprof
rebuild all packages
The final step in upgrading to a new language version of Ruby is the comprehensive rebuild of all existing packages that depend on Ruby, in their appropriate sequential order. This step is critical to ensure that all applications and libraries are compatible with the new Ruby version. This rebuild must be carefully managed to maintain dependency integrity.
- rebuild all packages in order
command to find packages to rebuild
./build-rebuild-todo-list.sh <old_ruby_version>