Beware: libzypp code cleanup - YAST related legacy code

Hi,

we found some YAST(?) related legacy code inside libzypp, which we will remove
in the next version unless someone speaks up now:

Introduced before 2005 during commit:


A) Creation of /var/log/YaST2/config_diff_DATE.log files including the first 25
lines of config file diffs upon .rpmnew/.rpmsave creation.


B) After a write to the config_diff_DATE.log
file, /var/lib/update-messages/yast2-packagemanager.rpmdb.configfiles is opened
and immediately closed again.


We plan to drop that code. If you need something like this, we can provide you a
callback sending the path of the 2 config files and you and create the diff as
you need it..



C) zypp::RpmDb::setBackupPath called from within yast-pkg-bindings,
src/Package.cc and available in ruby as Pkg.SetBackupPath().

This turns on creation of tarballs collecting the modified (binary) files of
each package before updating it. This simple kind of backup was introduced to
save self-compiled binaries/kernels before they were overwritten by rpm.

Whoever compiled a linux kernel on a pre-Pentium architecture known, why this
feature was valuable at that time.

We will for now deprecate the method and disable the backup. However it may be
that YAST still has has some 'Create backups during installation' button which
triggers a call to this, please remove it. It's wasted time and disk space most
probably.


Thanks.

--

cu,
Michael Andres

+------------------------------------------------------------------+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4
+------------------------------------------------------------------+
Michael Andres, E&I, ma@suse.com, Phone: ++49 (0)911 - 74 053-0
+------------------------------------------------------------------+
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg
Germany, (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer
+------------------------------------------------------------------+