On Tuesday 11 October 2005 10:13, Steve Grubb wrote:
So, why is kdemultimedia i386 installed?
This just gets better...
[root@spirit ~]# rpm -e kdemultimedia-3.4.91-1.i386
So far so good. No complaints from rpm and the disk drive made noise. Now, I
wonder if it left the 64 bit apps alone?
[root@spirit ~]# rpm -qV kdemultimedia-3.4.91-1.x86_64
.......T /etc/xdg/menus/applications-merged/kde-multimedia-music.menu
.......T /usr/share/apps/noatun/magictable
missing /usr/share/doc/HTML/en/artsbuilder
missing d /usr/share/doc/HTML/en/artsbuilder/apis.docbook
missing d /usr/share/doc/HTML/en/artsbuilder/arts-structure.png
missing d /usr/share/doc/HTML/en/artsbuilder/artsbuilder.docbook
missing d /usr/share/doc/HTML/en/artsbuilder/common
missing d /usr/share/doc/HTML/en/artsbuilder/detail.docbook
missing d /usr/share/doc/HTML/en/artsbuilder/digitalaudio.docbook
missing d /usr/share/doc/HTML/en/artsbuilder/faq.docbook
Nope. It ate the files from both packages. I don't think this is working quite
right. It seems that it had the smarts to overcome file conflicts when
installing the packages.
[root@spirit ~]# file /usr/bin/kmid
/usr/bin/kmid: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for
GNU/Linux 2.4.20, dynamically linked (uses shared libs), stripped
So, isn't it reasonable to assume it can handle conflicts at uninstall? It
should look at the file being removed and see if another package is also
claiming that file. If the checksum of the file matches the one in the
package being uninstalled, remove the file. Otherwise leave it alone.
-Steve