On Wednesday 05 August 2009 12:55:36 Jano Kupec wrote:
Michael Andres wrote:
On Tuesday 04 August 2009 20:45:41 Elmar Stellnberger wrote:
this can happen with any command (even 'zypper rm glibc'). I wonder why we ship the systemCheck with only glibc. Although it's up to the user to edit this file, why not put more stuff there?
/etc/zypp/systemCheck is a user config file and glibc is a simple example which does not hurt if being required. The original intent was to prevent zypper from accidentally cleaning the whole system, because zypper sets ForceResolve which allows the solver to consider deleting conflicting packages. But it should not be necessary any more, as zypp internally instructs the solver to keep 'rpm' installed. A suggested set of core packages would be product specific. In that case we had to offer an /etc/zypp/systemCheck.d directory, where products (the release-packages) could drop the definition of their 'core' sets. But the set of core packages is also defined by the dependencies of the release-package which represents your product (e.g openSUSE-release). So a product would have to write e.g: requires:openSUSE-release We can also leave it to the user to decide this. Maybe you want to change/remove a product, then those requirements are annoying. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org