Jérémy Bobbio: > Another idea: we stop running the test suite at build time for > ruby-rspec-mocks, ruby-rspec-expectations and ruby-rspec-core; and > instead, run all the test suites as part as building ruby-rspec. > > If we tighten the dependencies and build-dependencies in ruby-rspec, we > can happily remove the circular build dependency and at the same time > keep a good level of confidence in the fact that rspec gems are in > working conditions.
*sigh* I hope this would have been simpler. RSpec test suites relies on a quite specific environment to run and it is hard to reproduce it properly after the packages have been installed. Looks like this was not the best idea after all. I think RSpec eating its own dogfood for its test suite makes the problem similar to compiler bootstrap. The good news is that its actually simpler to bootstrap than compiler: * Do a first build with `DEB_BUILD_OPTIONS=nocheck` of ruby-rspec-core, ruby-rspec-expectations, ruby-rspec-mocks. This will create the binary packages without running the test suites (so the relevant Build-Depends can even be removed). * Rebuild the source packages using the binary packages built previously. This is not optimal but a pretty bearable work-around for now. -- Jérémy Bobbio .''`. [email protected] : :Ⓐ : # apt-get install anarchism `. `'` `-
signature.asc
Description: Digital signature
