From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-maintenance/package-moves/
Date: Thu, 23 Jan 2020 08:24:50 +0000 (UTC) [thread overview]
Message-ID: <1579767728.4b68e4039e4f0b1a484cac97c3a44c97e604b179.ulm@gentoo> (raw)
commit: 4b68e4039e4f0b1a484cac97c3a44c97e604b179
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Mon Dec 30 17:10:32 2019 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Thu Jan 23 08:22:08 2020 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=4b68e403
ebuild-maintenance/package-and-slot-moves: Add extra warnings
Since people are frequently getting moves wrong, try to point out a few
important limitations.
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
ebuild-maintenance/package-moves/text.xml | 22 +++++++++++++++++++++-
1 file changed, 21 insertions(+), 1 deletion(-)
diff --git a/ebuild-maintenance/package-moves/text.xml b/ebuild-maintenance/package-moves/text.xml
index 0d20667..a3a45c2 100644
--- a/ebuild-maintenance/package-moves/text.xml
+++ b/ebuild-maintenance/package-moves/text.xml
@@ -5,9 +5,29 @@
<body>
<p>
-This chapter describes the use of package and slot moves.
+This chapter describes the use of package and slot moves. The package update
+mechanism is a powerful tool, and needs to be used with caution. In particular,
+the following must be noted:
</p>
+<ol>
+ <li>
+ Updates are <e>not one-shot</e> operations and they are not stateful. All
+ updates can be reapplied multiple times to the same system, and all old
+ updates are applied to fresh Gentoo installations.
+ </li>
+ <li>
+ Once an update entry is created, the old package name (or slot) cannot be
+ reused. Attempting to reuse it will cause updates to apply again,
+ to the reused name. This also means that updates cannot be undone.
+ </li>
+ <li>
+ Updates can only perform one-to-one moves. They cannot be used to merge
+ packages. Attempting to move two or more packages into a single name may
+ cause serious problems for users.
+ </li>
+</ol>
+
</body>
<section>
next reply other threads:[~2020-01-23 8:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 8:24 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-08 11:15 [gentoo-commits] proj/devmanual:master commit in: ebuild-maintenance/package-moves/ Ulrich Müller
2024-02-08 10:39 Ulrich Müller
2022-02-18 18:19 Sam James
2022-01-22 21:35 Sam James
2022-01-22 21:35 Sam James
2022-01-22 21:35 Sam James
2022-01-22 21:35 Sam James
2020-01-23 8:24 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=1579767728.4b68e4039e4f0b1a484cac97c3a44c97e604b179.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