From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-lang/cfortran/
Date: Fri, 3 Jun 2022 12:27:48 +0000 (UTC) [thread overview]
Message-ID: <1654259083.2249b564d71300391f5a88461569f8f21408cddb.ulm@gentoo> (raw)
commit: 2249b564d71300391f5a88461569f8f21408cddb
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Fri Jun 3 12:24:43 2022 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Fri Jun 3 12:24:43 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2249b564
dev-lang/cfortran: Bump ebuild for 4.4 to EAPI 8
Keep keywords stable, since -r3 and -r4 produce identical images.
Bug: https://bugs.gentoo.org/817647
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
.../{cfortran-4.4-r3.ebuild => cfortran-4.4-r4.ebuild} | 15 ++++++---------
1 file changed, 6 insertions(+), 9 deletions(-)
diff --git a/dev-lang/cfortran/cfortran-4.4-r3.ebuild b/dev-lang/cfortran/cfortran-4.4-r4.ebuild
similarity index 84%
rename from dev-lang/cfortran/cfortran-4.4-r3.ebuild
rename to dev-lang/cfortran/cfortran-4.4-r4.ebuild
index 6776defb6db1..d5ccc7687463 100644
--- a/dev-lang/cfortran/cfortran-4.4-r3.ebuild
+++ b/dev-lang/cfortran/cfortran-4.4-r4.ebuild
@@ -1,9 +1,7 @@
-# Copyright 1999-2021 Gentoo Authors
+# Copyright 1999-2022 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
-EAPI=5
-
-inherit epatch
+EAPI=8
DEB_PR="14"
@@ -18,6 +16,8 @@ LICENSE="LGPL-2"
KEYWORDS="~alpha amd64 ~arm64 ~hppa ~ia64 ppc ppc64 ~riscv sparc x86 ~amd64-linux ~x86-linux"
IUSE="examples"
+PATCHES=( "${WORKDIR}"/${PN}_${PV}-${DEB_PR}.diff )
+
src_unpack() {
default
if use examples; then
@@ -28,10 +28,6 @@ src_unpack() {
fi
}
-src_prepare() {
- epatch "${WORKDIR}"/${PN}_${PV}-${DEB_PR}.diff
-}
-
src_install() {
insinto /usr/include/cfortran
doins cfortran.h
@@ -40,7 +36,8 @@ src_install() {
dodoc cfortran.doc debian/{NEWS,changelog,copyright}
- dohtml cfortran.html index.htm cfortest.c cfortex.f
+ docinto html
+ dodoc cfortran.html index.htm # cfortest.c cfortex.f
if use examples; then
insinto /usr/share/${PN}
next reply other threads:[~2022-06-03 12:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 12:27 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-11 8:39 [gentoo-commits] repo/gentoo:master commit in: dev-lang/cfortran/ WANG Xuerui
2025-01-11 8:39 WANG Xuerui
2025-01-11 8:39 WANG Xuerui
2024-04-08 18:50 Andrew Ammerlaan
2024-03-15 6:49 Sam James
2023-12-14 4:22 Sam James
2023-03-04 11:37 Arthur Zamarin
2023-03-04 8:49 Arthur Zamarin
2023-03-04 8:49 Arthur Zamarin
2023-03-04 8:07 Arthur Zamarin
2022-05-06 7:16 Arthur Zamarin
2022-05-06 7:08 Arthur Zamarin
2021-10-16 4:25 Sam James
2021-10-12 7:10 Agostino Sarubbo
2021-10-11 5:45 Sam James
2021-10-11 4:33 Sam James
2021-10-11 4:20 Sam James
2021-08-14 23:15 Marek Szuba
2021-08-14 23:15 Marek Szuba
2021-07-21 15:39 Marek Szuba
2019-11-06 9:56 Michał Górny
2019-10-16 4:45 Matt Turner
2019-10-11 22:32 Sergei Trofimovich
2019-10-07 19:27 Sergei Trofimovich
2019-10-07 19:12 Sergei Trofimovich
2019-10-07 10:44 Agostino Sarubbo
2018-05-16 22:57 Aaron Bauman
2017-07-17 9:48 Alexis Ballier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1654259083.2249b564d71300391f5a88461569f8f21408cddb.ulm@gentoo \
--to=ulm@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox