From: "Mike Frysinger" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/variables/
Date: Fri, 7 Aug 2015 05:08:51 +0000 (UTC) [thread overview]
Message-ID: <1438924118.fc94b7c5ee7672096abbfead15f956b887c6d5ba.vapier@gentoo> (raw)
commit: fc94b7c5ee7672096abbfead15f956b887c6d5ba
Author: Mike Frysinger <vapier <AT> gentoo <DOT> org>
AuthorDate: Fri Aug 7 05:08:38 2015 +0000
Commit: Mike Frysinger <vapier <AT> gentoo <DOT> org>
CommitDate: Fri Aug 7 05:08:38 2015 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=fc94b7c5
variables: SRC_URI: document the -> syntax
ebuild-writing/variables/text.xml | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/ebuild-writing/variables/text.xml b/ebuild-writing/variables/text.xml
index a31baa2..fd749c0 100644
--- a/ebuild-writing/variables/text.xml
+++ b/ebuild-writing/variables/text.xml
@@ -323,6 +323,30 @@ SRC_URI="http://example.com/files/${P}-core.tar.bz2
</body>
</subsection>
+
+<subsection>
+<title>Renaming Sources</title>
+<body>
+
+<p>
+Sometimes the upstream URI uses generic names that can easily clash with other
+packages when creating a single mirror. Using the <c>-></c> syntax allows
+you to rename the file when it's fetched from upstream for storing on mirrors
+and in the local distdir.
+</p>
+
+<p>
+Here we download a file from upstream which has a plain name like
+<c>1.0.tar.gz</c> and save/mirror it with a better name like
+<c>thepackage-1.0.tar.gz</c>.
+</p>
+
+<codesample lang="ebuild">
+SRC_URI="http://example.com/files/${PV}.tar.gz -> ${P}.tar.gz"
+</codesample>
+
+</body>
+</subsection>
</section>
<section>
next reply other threads:[~2015-08-07 5:09 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 5:08 Mike Frysinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-25 16:42 [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/variables/ Ulrich Müller
2022-08-25 16:42 Ulrich Müller
2022-08-25 16:42 Ulrich Müller
2022-02-18 18:19 Sam James
2022-02-16 18:43 Ulrich Müller
2022-02-16 18:02 Matthew Smith
2021-05-28 13:09 Ulrich Müller
2021-03-30 7:21 Ulrich Müller
2021-03-30 7:21 Ulrich Müller
2021-03-30 7:21 Ulrich Müller
2021-03-30 7:21 Ulrich Müller
2021-03-30 7:21 Ulrich Müller
2021-03-26 19:05 Ulrich Müller
2020-03-11 14:38 Ulrich Müller
2019-11-29 9:28 Ulrich Müller
2019-11-28 18:32 Göktürk Yüksek
2019-11-28 18:32 Göktürk Yüksek
2019-11-26 1:49 Göktürk Yüksek
2019-11-26 1:49 Göktürk Yüksek
2019-10-16 20:16 Göktürk Yüksek
2019-10-16 20:16 Göktürk Yüksek
2019-10-16 20:16 Göktürk Yüksek
2019-10-16 20:16 Göktürk Yüksek
2019-10-16 20:16 Göktürk Yüksek
2019-10-16 20:16 Göktürk Yüksek
2019-10-16 20:16 Göktürk Yüksek
2019-10-16 20:16 Göktürk Yüksek
2019-05-22 19:40 Göktürk Yüksek
2019-03-24 16:48 Ulrich Müller
2019-03-19 17:11 Brian Evans
2019-03-19 17:11 Brian Evans
2018-10-24 13:01 Brian Evans
2018-10-24 13:01 Brian Evans
2017-11-12 20:15 Ulrich Müller
2017-09-09 3:43 Göktürk Yüksek
2016-12-07 19:46 Göktürk Yüksek
2016-11-17 5:23 Göktürk Yüksek
2016-10-28 14:21 Göktürk Yüksek
2016-10-28 14:21 Göktürk Yüksek
2016-07-13 3:18 Göktürk Yüksek
2016-07-13 2:48 Göktürk Yüksek
2016-05-20 6:23 Göktürk Yüksek
2016-05-18 6:56 Göktürk Yüksek
2016-05-11 1:43 Mike Gilbert
2016-05-04 9:13 Göktürk Yüksek
2015-12-08 20:06 Ulrich Müller
2013-05-15 13:39 Dirkjan Ochtman
2013-05-15 13:39 Dirkjan Ochtman
2013-05-15 13:17 Dirkjan Ochtman
2012-11-24 19:12 Ulrich Mueller
2012-11-11 19:33 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=1438924118.fc94b7c5ee7672096abbfead15f956b887c6d5ba.vapier@gentoo \
--to=vapier@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