public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
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:18 +0000 (UTC)	[thread overview]
Message-ID: <1571256274.10c4cea8a800f9f921ca2dc3f6ea9303eea76861.gokturk@gentoo> (raw)

commit:     10c4cea8a800f9f921ca2dc3f6ea9303eea76861
Author:     Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
AuthorDate: Wed Oct 16 20:04:34 2019 +0000
Commit:     Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
CommitDate: Wed Oct 16 20:04:34 2019 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=10c4cea8

general-concepts/mirrors: rework the bad upstream distfile renaming example

If a distfile rename is necessary to cope with an upstream updating a
versioned distfile in place, suggest the format of '_YYYYMMDD' instead
of '.r*'. The rationale is that the '.r*' format may confuse readers
with the Gentoo ebuild revision format '-r*', for which there is no
necessary correlation. The timestamp format also has the added bonus
of quickly being able to tell when the distfile rename took place,
assuming the developer used the proper date for it.

Signed-off-by: Göktürk Yüksek <gokturk <AT> gentoo.org>

 general-concepts/mirrors/text.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/general-concepts/mirrors/text.xml b/general-concepts/mirrors/text.xml
index 42fef3f..11dd040 100644
--- a/general-concepts/mirrors/text.xml
+++ b/general-concepts/mirrors/text.xml
@@ -56,8 +56,8 @@ 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"
+# upstream updated the distfile in place, so suffix it with _YYYYMMDD
+SRC_URI="https://example.com/badupstream/${P}.tar.gz -> ${P}_20191016.tar.gz"
 </codesample>
 
 <p>


             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=1571256274.10c4cea8a800f9f921ca2dc3f6ea9303eea76861.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