Op maandag 21 juni 2004 06:59, schreef Mikus Grinbergs:
In my mind, dependency conflicts should behave "symmetrically". But to me it appears that APT was more paranoid than YaST. Whenever Mozilla 1.6 got installed on my system, and whenever those other 14 packages got installed, there were *no* warning messages. Yet, after receiving the warning from my attempted 1.7 install about 14 packages needing to be removed, I tried telling APT I wanted a "reinstall" of 1.6 -- and APT responded with the __same__ warning about needing to remove those same 14 packages !!
Apt is just strict, while Yast is more forgiven. By being more strict apt forces the package builder/provide to be more secure/precise, which may result in the end in an easier package installation and a smooth running system. It's all about keeping the rpmdb database in a consistent state.
Which suse version?
9.1 (see the 'Subject:' line)
Ah, I didn't look at that.
I have no problems installing mozilla-1.7 on a standard suse system (kept up to date solely with apt):
linux:~ # apt -s install mozilla Reading Package Lists... Done Building Dependency Tree... Done The following packages will be upgraded mozilla The following packages will be REMOVED: epiphany epiphany-plugins 1 upgraded, 0 newly installed, 2 removed and 17 not upgraded. Remv epiphany (1.0.7-64 suse:9.1/stable, SuSE:9.1/stable) Remv epiphany-plugins (0.1.2-225 suse:9.1/stable, SuSE:9.1/stable)
You too had Epiphany being removed. And my standard SuSE system still shows an icon for Epiphany in the default Gnome taskbar !!
I use kde, so I didn't (don't) see the side effect on the gnome desktop. -- Richard Bos Without a home the journey is endless