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/ebuild-revisions/
Date: Mon, 25 Sep 2017 04:23:12 +0000 (UTC) [thread overview]
Message-ID: <1506312626.c487cdb2874911a5495f2f05dae89d4253fa260f.gokturk@gentoo> (raw)
commit: c487cdb2874911a5495f2f05dae89d4253fa260f
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Aug 6 11:45:35 2017 +0000
Commit: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
CommitDate: Mon Sep 25 04:10:26 2017 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=c487cdb2
general-concepts/ebuild-revisions: Clearly define the purpose of revisions
general-concepts/ebuild-revisions/text.xml | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/general-concepts/ebuild-revisions/text.xml b/general-concepts/ebuild-revisions/text.xml
index f2d7234..b0c0d97 100644
--- a/general-concepts/ebuild-revisions/text.xml
+++ b/general-concepts/ebuild-revisions/text.xml
@@ -13,6 +13,20 @@ An ebuild with no explicit revision number has the implicit <c>-r0</c>
revision.
</p>
+<p>Ebuild revisions usually serve two purposes:</p>
+<ol>
+ <li>
+ keeping an older copy of an ebuild around when doing a potentially
+ breaking change, and
+ </li>
+
+ <li>
+ propagating the rebuild of a package when performing a meaningful
+ change that would otherwise go unnoticed by users who have installed
+ the current version already.
+ </li>
+</ol>
+
<p>
Ebuilds should have their <c>-rX</c> incremented whenever a change is made which
will make a substantial difference to what gets installed by the package <d/> by
next reply other threads:[~2017-09-25 4:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 4:23 Göktürk Yüksek [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-29 17:40 [gentoo-commits] proj/devmanual:master commit in: general-concepts/ebuild-revisions/ Ulrich Müller
2024-10-29 17:40 Ulrich Müller
2023-08-26 5:43 Ulrich Müller
2023-01-14 20:24 Sam James
2022-11-10 7:17 Sam James
2022-11-10 7:17 Sam James
2021-09-24 14:07 Ulrich Müller
2021-09-24 12:00 Joonas Niilola
2021-09-24 12:00 Joonas Niilola
2021-09-24 12:00 Joonas Niilola
2021-09-24 12:00 Joonas Niilola
2021-07-03 16:21 Ulrich Müller
2021-07-03 16:21 Ulrich Müller
2017-09-25 4:23 Göktürk Yüksek
2017-09-25 4:23 Göktürk Yüksek
2017-09-25 4:23 Göktürk Yüksek
2015-05-09 15:22 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=1506312626.c487cdb2874911a5495f2f05dae89d4253fa260f.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