From: "Göktürk Yüksek" <gokturk@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: general-concepts/mirrors/
Date: Wed, 16 Oct 2019 20:16:17 +0000 (UTC) [thread overview]
Message-ID: <1571255617.3c24f9dfdfd76d2ea0ca3b7015afaa62b43cff99.gokturk@gentoo> (raw)
commit: 3c24f9dfdfd76d2ea0ca3b7015afaa62b43cff99
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Oct 6 07:59:33 2019 +0000
Commit: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
CommitDate: Wed Oct 16 19:53:37 2019 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=3c24f9df
general-concepts/mirrors: Update the method of replacing files
The modern method of replacing repackaged distfiles is to rename them
using SRC_URI arrows, not do some mirror-replacement voodoo.
Acked-by: Michael Orlitzky <mjo <AT> gentoo.org>
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
Signed-off-by: Göktürk Yüksek <gokturk <AT> gentoo.org>
general-concepts/mirrors/text.xml | 28 ++++++++++++++++++----------
1 file changed, 18 insertions(+), 10 deletions(-)
diff --git a/general-concepts/mirrors/text.xml b/general-concepts/mirrors/text.xml
index 7cc6b76..24dc188 100644
--- a/general-concepts/mirrors/text.xml
+++ b/general-concepts/mirrors/text.xml
@@ -50,16 +50,24 @@ found. This should only be used if a license requires it.
<title>Replacing Automatically Mirrored Files</title>
<body>
<p>
-On rare occasions you may need to replace a file that is already mirrored. In this case proceed as
-follows:
-<ol>
- <li>Put a copy of the new distfile on dev.gentoo.org into /space/distfiles-local</li>
- <li>commit the new manifest to the git tree</li>
- <li>wait</li>
-</ol>
-After a few hours a cron job on dev.gentoo.org will fetch the file and replace the version on the
-mirrors. The file will be automatically removed from /space/distfiles-local after approximately two
-weeks.
+On rare occasions you may need to replace a file that is already mirrored.
+This is usually the case when upstream remakes a release package. If this
+is necessary, please use <c>SRC_URI</c> arrow to rename the file. For example:
+</p>
+
+<codesample lang="ebuild">
+# upstream updated the distfile in place, so make it .r1
+SRC_URI="https://example.com/badupstream/${P}.tar.gz -> ${P}.r1.tar.gz"
+</codesample>
+
+<p>
+Since Gentoo mirrors operate using local distfile names, they will automatically
+fetch and start distributing the new version.
+</p>
+
+<p>
+Please note that if upstream made any changes affecting the built package,
+you need to also bump the ebuild's revision.
</p>
<p>
next reply other threads:[~2019-10-16 20:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 20:16 Göktürk Yüksek [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-10 10:19 [gentoo-commits] proj/devmanual:master commit in: general-concepts/mirrors/ Joonas Niilola
2019-12-18 21:56 Göktürk Yüksek
2019-12-18 21:56 Göktürk Yüksek
2019-11-26 13:40 Ulrich Müller
2019-10-29 20: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-03-19 17:11 Brian Evans
2016-06-16 22:46 Göktürk Yüksek
2016-02-05 12:59 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
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=1571255617.3c24f9dfdfd76d2ea0ca3b7015afaa62b43cff99.gokturk@gentoo \
--to=gokturk@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