Ruby/Migration

This scheme migration rules

1. all the Requires dependencies for all the subpackages are determined automatically, so that all the dependencies of suck kind must be rejected;
2. BuildRequires dependencies for the package in case when testing shell be executed (see %check section), or when it is really necessary to do, must be explicitly defined, and can be got by the setup.rb application;
3. when the package has been renamed, it is required to explicitly define the old package name in Provides and Obsoletes keywords;
4. In the %prep all the macros pointing to ruby are rejected, in particular %update_setup_rb;
5. In the %build all the macros pointing to ruby are replaced with %ruby_build, with %ruby_config in particular %ruby_build;
6. In the %install all the macros pointing to ruby are replaced with %ruby_install;
7. In the %check all the macros pointing to ruby are replaced with %ruby_test, although in case of the extremely and urgent need this macro can be grayed out;
8. In the %files class sections the following rules of replacement are applied: %[ruby]gem_specdir to %ruby_gemspecdir, %ruby_vendorlibdir to %ruby_gemlibdir, %ruby_vendorarchdir to %ruby_gemextdir;
9. In the %files for documentation %ruby_ri_sitedir is replaced with %ruby_gemdocdir.