Remove repackage support to finish off with rollback

The two main classes of rollback/repackage need are
1) Gimme back the previous version, this broke XYZ on my system.
   This is better handled by downgrading to the previous version of original
   package instead of repackaged garbage. We should maintain real package
   (version) history somewhere.

2) Upgrade messed up my configuration.
   Instead of repackaging everything we could be far more intelligent
   wrt config files, stick them into real version control or at least have
   hooks to do so.

RPMCALLBACK_REPACKAGE_* and RPMTRANS_FLAG_REPACKAGE definitions left around
to avoid needlessly breaking everybodys callbacks (for now)

1 files changed, 0 insertions, 16 deletions

diff --git a/macros.in b/macros.in
index baf9cc6d9..e4cd2dfb5 100644
--- a/macros.in
+++ b/macros.in
@@ -713,22 +713,6 @@ print (t)\
 # XXX	Note: escaped %% for use in headerSprintf()
 #%_solve_name_fmt	%{?_solve_pkgsdir}%%{NAME}-%%{VERSION}-%%{RELEASE}.%%{ARCH}.rpm
 
-#	The output binary package file name template used when repackaging
-#	erased packages.
-#
-# XXX	Note: escaped %% for use in headerSprintf()
-%_repackage_name_fmt	%%{NAME}-%%{VERSION}-%%{RELEASE}.%%{ARCH}.rpm
-
-#	The directory in which erased packages will be saved when using
-#	the --repackage option.
-%_repackage_dir		/var/spool/repackage
-
-#	A path (i.e. URL) prefix that is pre-pended to %{_repackage_dir}.
-%_repackage_root	%{nil}
-
-#	If non-zero, all erasures will be automagically repackaged.
-%_repackage_all_erasures	0
-
 #	Verify digest/signature flags for various rpm modes:
 #	0x30300 (_RPMVSF_NODIGESTS)    --nohdrchk      if set, don't check digest(s)
 #	0xc0c00 (_RPMVSF_NOSIGNATURES) --nosignature   if set, don't check signature(s)