dev-libs/mpfr: epatch->eapply

Nothing to test, as these ebuilds do not actually have a patchset to apply. Just know that for each new patchset made, they will need to be -p1 applicable. Package-Manager: Portage-2.3.31, Repoman-2.3.9 Signed-off-by: Anthony G. Basile <[email protected]>
johu · Apr 24, 2018 · 5b46714 · 5b46714
1 parent eb2e05c
commit 5b46714
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/dev-libs/mpfr/mpfr-4.0.0-r1.ebuild b/dev-libs/mpfr/mpfr-4.0.0-r1.ebuild
@@ -29,7 +29,7 @@ src_prepare() {
 	if [[ ${PLEVEL} != ${PV} ]] ; then
 		local i
 		for (( i = 1; i <= PLEVEL; ++i )) ; do
-			epatch "${FILESDIR}"/${MY_PV}/patch$(printf '%02d' ${i})
+			eapply "${FILESDIR}"/${MY_PV}/patch$(printf '%02d' ${i})
 		done
 	fi
 	eapply_user

diff --git a/dev-libs/mpfr/mpfr-4.0.1.ebuild b/dev-libs/mpfr/mpfr-4.0.1.ebuild
@@ -29,7 +29,7 @@ src_prepare() {
 	if [[ ${PLEVEL} != ${PV} ]] ; then
 		local i
 		for (( i = 1; i <= PLEVEL; ++i )) ; do
-			epatch "${FILESDIR}"/${MY_PV}/patch$(printf '%02d' ${i})
+			eapply "${FILESDIR}"/${MY_PV}/patch$(printf '%02d' ${i})
 		done
 	fi
 	eapply_user