Roger Oberholtzer wrote:
Should this also delete an already installed QT4 on a client computer? When doing a zypper dup on a Tumbleweed system today, it reported:
The following 30 packages are going to be REMOVED:
breeze4-style kde4-filesystem kdebase4-runtime kdebase4-workspace-libs kdelibs4 kdelibs4-branding-upstream kdelibs4-core libaccounts-glib0 libattica0_4 libbreezecommon4-5 libdav1d2 libdbusmenu-qt2 libdvdread4 libkactivities6 libkde4 libkdecore4 libksuseinstall1 libldb1 libldb1-32bit libphonon4 libpolkit-qt-1-1 libqt4 libqt4-devel libqt4-linguist libqt4-qt3support libqt4-sql libqt4-sql-sqlite libqt4-x11 phonon-backend-gstreamer sni-qt
I'm not using KDE4. But I have some Python programs that use QT4. They will eventually be updated. But until then, on systems where QT4 is already installed, removing QT4 seems strict. No problem that it goes away in the build system and can no longer be installed. But removing it from installed systems may be a surprise to many.
Yes, that's one drawback of the way TW handles things, I've been bitten by that several times already. Packages that no longer are in the repo, and are not requested by any other package, get removed. This, though understandable from distributor side, is extremely inconvenient for people installing (self-compiled) stuff in, e.g., /usr/local. So either use locks, or convert your local programs to packages with the necessary dependencies. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org