ruby-ng.eclass: make presence of RUBY_PATCHES fatal

The eqawarn in EAPI 6 is easy to mis and may lead to patches
"silently" not being applied. die on this in EAPI 7 to make this
situation more explicit.

Signed-off-by: Hans de Graaff <graaff@gentoo.org>

diff --git a/eclass/ruby-ng.eclass b/eclass/ruby-ng.eclass
index 7fef1085a9dde85476959744bcd28049865cec23..59d4450a9954d6bd043ddbea2fefed0551e7022e 100644 (file)
--- a/eclass/ruby-ng.eclass
+++ b/eclass/ruby-ng.eclass
@@ -420,11 +420,16 @@ _ruby_apply_patches() {
                                fi
                        done
                        ;;
-               *)
+               6)
                        if [[ -n ${RUBY_PATCHES[@]} ]]; then
                           eqawarn "RUBY_PATCHES is no longer supported, use PATCHES instead"
                        fi
                        ;;
+               *)
+                       if [[ -n ${RUBY_PATCHES[@]} ]]; then
+                               die "RUBY_PATCHES is no longer supported, use PATCHES instead"
+                       fi
+                       ;;
        esac
 
        # This is a special case: instead of executing just in the special