After more than 3 years, the review request for package rubygem-passenger can finally move forward.
A bundling exception was finally granted, because someone is putting in the work to make the bundled, forked and patched version of Boost ultimately dissappear - by bringing the required changes upstream.
While I proposed doing so early on in the saga, though I could not do it myself and would have needed to find someone else to do so, that wasn't acceptable - as is tradition in the Fedora Project by now, the "discussion" on my plan of attack went absolutely nowhere, with people arguing in circles, simply for the sake of arguing, and without ever having been, being or feeling endangered of being involved in any way, shape or form.
Patience is golden, the cost of running Passenger in my own build systems can now be avoided. Time for 3.0.12 to be packaged for Rawhide, built against Ruby 1.9, and the review to move along!
So, I've finally done it, and I'd like to think I've come a long way.
Having focussed on how to make available for everyone, Ruby 1.9.1 without the implied requirement of having to run an unstable Rawhide and us (the Ruby SIG) running around in circles trying to figure out stuff as we go along, meanwhile compromising the development path of a single Fedora release (6 months, you know, is very, very short, especially with freezes and deadlines and such).
Ergo, here we go with a repository for all enthusiasts: http://mirror.nl.ergo-project.org/repositories/feature-f12-ruby-1.9.1/
For a proper installation of the configuration of such repository, which still is in the "let's figure this thing out" stage, use the -release package; It'll install the yum repository configuration for you.
Please, pretty-please provide your feedback. You can reach us over the Ruby SIG mailing list, or me personally via commenting on this blog post, or sending me a message at email@example.com.
Worth mentioning is that I've made sure the minimal stack allows installation: ruby and puppet. If not your own personal development laptop, at least you can continuously manage a set of servers running with this Ruby 1.9.1 stack, and thus revert any change that does not break puppet itself ;-)