From: "Florian Schmaus" <flow@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: gui-wm/river/
Date: Sat, 28 Dec 2024 20:08:11 +0000 (UTC) [thread overview]
Message-ID: <1735416333.295f6f8eb933542c5c69300e22e74553e1ddab35.flow@gentoo> (raw)
Message-ID: <20241228200811.PntwwWgZjT8S-XmhgwiaIU8NHXzYlGTwDxTGwn66tfQ@z> (raw)
commit: 295f6f8eb933542c5c69300e22e74553e1ddab35
Author: Florian Schmaus <flow <AT> gentoo <DOT> org>
AuthorDate: Sat Dec 28 20:05:25 2024 +0000
Commit: Florian Schmaus <flow <AT> gentoo <DOT> org>
CommitDate: Sat Dec 28 20:05:33 2024 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=295f6f8e
gui-wm/river: drop unnecessary definition of src_unpack()
Since zig_src_unpack() is an exported phase function of zig.eclass, so
there is no need to explictily define src_unpack() (if no other
inherited eclass also exports src_unpack(), which is not the case for
this ebuild).
Signed-off-by: Florian Schmaus <flow <AT> gentoo.org>
gui-wm/river/river-0.3.6.ebuild | 4 ----
1 file changed, 4 deletions(-)
diff --git a/gui-wm/river/river-0.3.6.ebuild b/gui-wm/river/river-0.3.6.ebuild
index 1342330ce..6ddf852d6 100644
--- a/gui-wm/river/river-0.3.6.ebuild
+++ b/gui-wm/river/river-0.3.6.ebuild
@@ -52,10 +52,6 @@ PATCHES=( "${FILESDIR}/${P}-fix-no-lazypath.patch" )
DOCS=( "README.md" )
-src_unpack() {
- zig_src_unpack
-}
-
src_configure() {
local my_zbs_args=(
-Dstrip=false # Let Portage control this
next reply other threads:[~2024-12-28 20:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-28 20:06 Florian Schmaus [this message]
2024-12-28 20:08 ` [gentoo-commits] repo/proj/guru:master commit in: gui-wm/river/ Florian Schmaus
-- strict thread matches above, loose matches on Subject: below --
2025-03-07 15:56 [gentoo-commits] repo/proj/guru:dev " Eric Joldasov
2025-01-24 8:56 Eric Joldasov
2024-12-28 20:07 Florian Schmaus
2024-08-15 17:37 Eric Joldasov
2024-08-04 17:32 Daichi Yamamoto
2024-08-04 9:52 Eric Joldasov
2024-08-04 8:14 Daichi Yamamoto
2024-08-04 7:11 Daichi Yamamoto
2022-12-01 21:35 Cara Salter
2022-11-28 18:28 Cara Salter
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=1735416333.295f6f8eb933542c5c69300e22e74553e1ddab35.flow@gentoo \
--to=flow@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