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 <[email protected]>
hanetzer · Jul 25, 2019 · c37a064 · c37a064
1 parent cda96c4
commit c37a064
Showing 1 changed file with 6 additions and 1 deletion.
diff --git 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