Mailing List Archive

[PATCH 3/6] ruby-ng.eclass: make presence of RUBY_PATCHES fatal
From: Hans de Graaff <graaff@gentoo.org>

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>
---
eclass/ruby-ng.eclass | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)

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
--
2.21.0