https://bugzilla.novell.com/show_bug.cgi?id=367057
User support@microtechniques.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=367057#c10
--- Comment #10 from Don Hughes 2008-04-17 16:25:30 MST ---
Stefan,
Thanks,
I do. In general, in order to increase performance and reduce attack vectors,
I only compile with the very minimum options necessary to run the applications
in my environment. SuSE tends to compile with the maximum reasonable set for
the widest compatibility.
Previous verify runs ran cleanly, but this update modified one of the dependent
packages to require a new feature that was available in the SuSE apache, but
not in mine. But instead of giving a message so that I could stop the update,
investigate, recompile my version etc; it just 'updated' my version to the
SuSE version.
With the second example, the problem was not that I was using packages
installed outside of the RPM system, but that I had uninstalled a number of
packages that were install with the 'minimal system install', but that I did
not want on my system. The update logic decided that since I was missing part
of the 'package group' and because there were several conflicts, that it would
just go ahead and resolve the conflicts by deleting the rest of the group --
which was, basically, the entire operating system.
For example, I uninstalled required libraries that, although required for some
applications, were for features that I will never use, and, in fact, do not
want to be used. The only risk should be a potential program crash if that
function somehow managed to get called, not that the update logic would
unilaterly uninstall the applicaton.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
