From 718a01fdf522c8d02e7a1d4ffb80b28c8555c483 Mon Sep 17 00:00:00 2001
From: Thierry Vignaud <tv@mageia.org>
Date: Fri, 5 Oct 2012 16:04:37 +0000
Subject: drop --repackage option (non working since rpm-4.6 in 2009)

should have been done right after commit r251061 by pixel on Tue Jan
2009: "- drop urpmi.recover
(no more possible with rpm 4.6 which doesn't handle --repackage)"
---
 pod/8/urpmi.pod | 12 ------------
 1 file changed, 12 deletions(-)

(limited to 'pod/8/urpmi.pod')

diff --git a/pod/8/urpmi.pod b/pod/8/urpmi.pod
index 508a5ed2..c9fd27a4 100644
--- a/pod/8/urpmi.pod
+++ b/pod/8/urpmi.pod
@@ -349,18 +349,6 @@ architecture of the host. This is equivalent to C<rpm --ignorearch>.
 Don't check file systems for sufficient disk space before installation.
 This is equivalent to C<rpm --ignoresize>.
 
-=item B<--repackage>
-
-Save previous state of upgraded packages; in other words, save the old
-rpms (usually in F</var/spool/repackage>, but you can override this with
-an rpm macro.) This is equivalent to providing the B<--repackage> flag to
-rpm.
-
-I<Note:> if you use C<urpmi.recover> to set up a repackage policy, you
-don't need this option, because C<urpmi.recover> will globally override
-the appropriate rpm macro that enables repacking of all rpm transactions
-system-wide.
-
 =item B<--noscripts>
 
 Don't execute the scriptlets.
-- 
cgit v1.2.1