I have attached two examples, you can compare these with the way smart
handles conflicts. My solution is simple; just automatically remove the
conflicting files and let the user know you are doing that. Or provide
sane default setting which can be easily agreed upon.
On Tue, 2007-10-09 at 15:13 +0200, Stefan Hundhammer wrote:
> On Tuesday 09 October 2007 14:47, Aniruddha wrote:
> > Thank you for your answer. Do you happen to know why smart is able to
> > make these dependency adjustments automatically?
>
> Are you actually comparing the same scenarios?
>
> Dependency problems are something no user likes to be confronted with. So we
> try to resolve as many of them as possible. The ones that are left are the
> ones that get reported to the user. If we knew any reasonable way (that works
> in every case, not just in some) to handle them automatically, we would.
>
> Could you come up with some real dependency problems you were confronted with
> and with some suggestions how to handle them automatically? Hint: You can
> export the problem report to text file from that dialog's "Expert" menu
> button; you could paste the result here. This kind of discussion becomes very
> abstract really quickly without real examples.
>
>
> CU
> --
> Stefan Hundhammer <[EMAIL PROTECTED]> Penguin by conviction.
> YaST2 Development
> SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
> Nürnberg, Germany
#### YaST2 conflicts list - generated 2007-10-09 17:19:46 ####
Cannot install yast2-theme-openSUSE-Crystal, because it is conflicting with
yast2-theme-openSUSE
A conflict over yast2-theme-openSUSE-Crystal == 2.15.14-4
(yast2-theme-openSUSE-Crystal) requires the removal of
yast2-theme-openSUSE-Crystal-2.15.14-4.noarch[openSUSE-10.3-FTP_10.3] which is
scheduled for installation
=== yast2-theme-openSUSE-Crystal-2.15.14-4.noarch[openSUSE-10.3-FTP_10.3]
===
yast2-theme-openSUSE-Crystal-2.15.14-4.noarch[openSUSE-10.3-FTP_10.3]
will be installed by the user.
hicolor-icon-theme-0.10-37.noarch is needed by
yast2-theme-openSUSE-Crystal-2.15.14-4.noarch[openSUSE-10.3-FTP_10.3]
(hicolor-icon-theme == 0.10-37)
bash-3.2-61.i586 is needed by
yast2-theme-openSUSE-Crystal-2.15.14-4.noarch[openSUSE-10.3-FTP_10.3] (/bin/sh)
6 more...
Conflict Resolution:
( ) do not install yast2-theme-openSUSE-Crystal
( ) delete yast2-theme-openSUSE
( ) Ignore this conflict of yast2-theme-openSUSE-Crystal
pattern:yast2_basis has missing dependencies
There are no installable providers of yast2-theme-openSUSE for
pattern:yast2_basis-10.3-159.i586
=== pattern:yast2_basis-10.3-159.i586 ===
yast2-theme-openSUSE-2.15.14-4.noarch[openSUSE-10.3-FTP_10.3] provides
yast2-theme-openSUSE == 2.15.14-4, but it is uninstallable. Try installing it
on its own for more details.
yast2-theme-openSUSE-2.15.14-4.noarch provides yast2-theme-openSUSE ==
2.15.14-4, but is scheduled to be uninstalled.
pattern:yast2_basis-10.3-159.i586 depends on yast2-theme-openSUSE
pattern:yast2_basis-10.3-159.i586 is lacking the requirement
yast2-theme-openSUSE
(null)
Conflict Resolution:
( ) delete yast2_basis
( ) Ignore this requirement just here
#### YaST2 conflicts list END ###
#### YaST2 conflicts list - generated 2007-10-09 17:26:44 ####
gcc-c++ has missing dependencies
There are no alternative providers of gcc installed for gcc-c++-4.2-24.i586
=== gcc-c++-4.2-24.i586 ===
gcc-4.2-24.i586 provides gcc == 4.2-24, but is scheduled to be
uninstalled.
gcc-4.2-24.i586[openSUSE-10.3-FTP_10.3] provides gcc == 4.2-24, but has
another architecture.
gcc-c++-4.2-24.i586 depends on gcc
gcc-c++-4.2-24.i586 is lacking the requirement gcc
(null)
Conflict Resolution:
( ) keep gcc
( ) delete gcc-c++
( ) Ignore this requirement just here
( ) Generally ignore this requirement
pattern:devel_basis has missing dependencies
There are no alternative providers of gcc installed for
pattern:devel_basis-10.3-159.i586
=== pattern:devel_basis-10.3-159.i586 ===
gcc-4.2-24.i586 provides gcc == 4.2-24, but is scheduled to be
uninstalled.
gcc-4.2-24.i586[openSUSE-10.3-FTP_10.3] provides gcc == 4.2-24, but has
another architecture.
pattern:devel_basis-10.3-159.i586 depends on gcc
pattern:devel_basis-10.3-159.i586 is lacking the requirement gcc
(null)
Conflict Resolution:
( ) keep gcc
( ) delete devel_basis
( ) Ignore this requirement just here
( ) Generally ignore this requirement
pattern:devel_kernel has missing dependencies
There are no alternative providers of devel_basis installed for
pattern:devel_kernel-10.3-159.i586
=== pattern:devel_kernel-10.3-159.i586 ===
pattern:devel_basis-10.3-159.i586 provides devel_basis == 10.3-159, but
is scheduled to be uninstalled.
pattern:devel_basis-10.3-159.i586[openSUSE-10.3-FTP_10.3] provides
devel_basis == 10.3-159, but it is uninstallable. Try installing it on its own
for more details.
pattern:devel_kernel-10.3-159.i586 depends on devel_basis
pattern:devel_kernel-10.3-159.i586 is lacking the requirement
devel_basis
(null)
Conflict Resolution:
( ) keep devel_basis
( ) delete devel_kernel
( ) Ignore this requirement just here
( ) Generally ignore this requirement
pattern:devel_rpm_build has missing dependencies
There are no alternative providers of gcc installed for
pattern:devel_rpm_build-10.3-159.i586
=== pattern:devel_rpm_build-10.3-159.i586 ===
gcc-4.2-24.i586 provides gcc == 4.2-24, but is scheduled to be
uninstalled.
gcc-4.2-24.i586[openSUSE-10.3-FTP_10.3] provides gcc == 4.2-24, but has
another architecture.
pattern:devel_rpm_build-10.3-159.i586 depends on gcc
pattern:devel_rpm_build-10.3-159.i586 is lacking the requirement gcc
(null)
Conflict Resolution:
( ) keep gcc
( ) delete devel_rpm_build
( ) Ignore this requirement just here
( ) Generally ignore this requirement
#### YaST2 conflicts list END ###
