diff options
| author |   Michał Górny <mgorny@gentoo.org> | 2019-12-30 18:10:32 +0100 |
|---|---|---|
| committer |   Ulrich Müller <ulm@gentoo.org> | 2020-01-23 09:22:08 +0100 |
| commit | 4b68e4039e4f0b1a484cac97c3a44c97e604b179 (patch) | |
| tree | 01843ad0dcb4ecdd75fe6f0b6ee0ab8dfa9a1c2e | |
| parent | ebuild-maintenance/maintenance-tasks: Drop "Homepage unavailable" section. (diff) | |
| download | devmanual-4b68e4039e4f0b1a484cac97c3a44c97e604b179.tar.gz devmanual-4b68e4039e4f0b1a484cac97c3a44c97e604b179.tar.bz2 devmanual-4b68e4039e4f0b1a484cac97c3a44c97e604b179.zip | |
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@gentoo.org>
Signed-off-by: Ulrich Müller <ulm@gentoo.org>
| -rw-r--r-- | ebuild-maintenance/package-moves/text.xml | 22 |
1 files changed, 21 insertions, 1 deletions
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> |