On 02/10/2010 08:44 AM, Jay_Linux wrote:
I don't see this option in Yast (using the Gtk interface in GNOME 2.28 desktop). ..... (/ Can Yast be made to use the Qt interface in GNOME ?, since I am unable to use KDE 4.3.5 as there is a problem in the desktop icons (red exclamation mark on desktop icons and apps don't launch, and thus would prefer to use KDE 3.5.10 if it offers the same functionality and apps as KDE 4 does /).
- Another thing is: does one need to make a change in any of the system files in _oS 11.2_ when KDE 4 & KDE 3 are co-installed, as mentioned here - (/ didn't have any problem with both KDE's installed in _oS 11.1_ /)
Whoaaaa! I use gnome too, but for ANYTHING LIKE THIS, use ONLY: yast2 --qt sw_single & The 11.2 yast2 --gtk interface provides nowhere near the control required for any package customization. In the --qt interface IIRC, you will have the option at the top of the package list or in the "Versions" tab to (AllowVendorChange) to switch all package versions to those found in repository XYZ. After you start yast and select Filter -> Repositories and then select the kde3 repository, (and each the kde3 community and playground repos) you will need to Allow Vendor Change for the entire repository, unless you employ the (personally recommended, but not 'Officially' recommended) work-around by setting AllowVendorChange=true in /etc/zypp/zypp.conf. Without AllowVendorChange=true, 11.2 will refuse to show you the newer kde3 packages from the kde3 repo (or community or playground repos). The default AllowVendorChange=false just tells yast/zypper that when it finds a version of a package contained in any repository that is newer than the official release package -> hide it from the user unless he specifically says use it (this is a huge pain when updating a large number of packages). It is a feature that is supposed to prevent against users installing incompatible libraries or packages from different repos. As long as you resolve your dependencies in a sane manner anyway during package selection, zypper dependency checking is more than good enough the way it was before this 11.2 hidden restriction. I found that option much more of a pain than of any real usefulness and ended up disabling the vendor lock (setting AllowVendorChange=true) in zypp.conf to get back the normal zypper behavior. Just make sure you solve your dependency conflicts like you have always done and you will be fine -- but you will need the control provided by yast2 --qt to do it correctly. The yast2 --gtk version is for users who don't want to (or can't) think. I tried using it in gnome and it drove me crazy. It was impossible to see and navigate through a large number of packages and getting to the dependency details was near impossible. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org