From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/functions/src_unpack/rpm-sources/
Date: Sat, 14 Sep 2024 19:11:54 +0000 (UTC) [thread overview]
Message-ID: <1726341058.a166928ab188ff3b108d9a2651217dd96828b282.ulm@gentoo> (raw)
commit: a166928ab188ff3b108d9a2651217dd96828b282
Author: Sebastian Engel <sighunter <AT> gmx <DOT> de>
AuthorDate: Wed Aug 28 11:13:20 2024 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Sat Sep 14 19:10:58 2024 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=a166928a
src_unpack/rpm-sources: Replace src_unpack override example code
This replaces the code example with a snippet of how it is currently used in
::gentoo/dev-util/intel-ocl-sdk/intel-ocl-sdk-18.1.0.015.ebuild
because the old example code had multiple issues.
Signed-off-by: Sebastian Engel <sighunter <AT> gmx.de>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
ebuild-writing/functions/src_unpack/rpm-sources/text.xml | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/ebuild-writing/functions/src_unpack/rpm-sources/text.xml b/ebuild-writing/functions/src_unpack/rpm-sources/text.xml
index 0029c53..99c932e 100644
--- a/ebuild-writing/functions/src_unpack/rpm-sources/text.xml
+++ b/ebuild-writing/functions/src_unpack/rpm-sources/text.xml
@@ -25,10 +25,8 @@ manner such as:
<codesample lang="ebuild">
src_unpack() {
- rpm_src_unpack ${A}
- cd "${S}"
-
- use ssl && eapply "${FILESDIR}/${PV}/${P}-ssl.patch"
+ unpack ${A}
+ rpm_unpack "${S}/rpm/intel-openclrt-${PV}-${ALT_PV}.x86_64.rpm"
}
</codesample>
next reply other threads:[~2024-09-14 19:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-14 19:11 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-09 4:24 [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/functions/src_unpack/rpm-sources/ Sam James
2021-03-12 19:32 Ulrich Müller
2018-09-14 16:55 Brian Evans
2013-02-16 0:08 Markos Chandras
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=1726341058.a166928ab188ff3b108d9a2651217dd96828b282.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