summaryrefslogtreecommitdiff
path: root/eclass
diff options
context:
space:
mode:
authorHans de Graaff <graaff@gentoo.org>2019-07-21 08:27:50 +0200
committerHans de Graaff <graaff@gentoo.org>2019-07-25 08:09:41 +0200
commitc37a064beb441dcefd21457ac9d3a15cc55817f2 (patch)
tree169868028b3e9834663aca1a685da19ee63e7b75 /eclass
parentruby-ng.eclass: stop inheriting toolchain-funcs (diff)
downloadgentoo-c37a064beb441dcefd21457ac9d3a15cc55817f2.tar.gz
gentoo-c37a064beb441dcefd21457ac9d3a15cc55817f2.tar.bz2
gentoo-c37a064beb441dcefd21457ac9d3a15cc55817f2.zip
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>
Diffstat (limited to 'eclass')
-rw-r--r--eclass/ruby-ng.eclass7
1 files changed, 6 insertions, 1 deletions
diff --git a/eclass/ruby-ng.eclass b/eclass/ruby-ng.eclass
index 7fef1085a9dd..59d4450a9954 100644
--- 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