Linked by Thom Holwerda on Wed 16th May 2007 22:55 UTC
Thread beginning with comment 241502
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



Member since:
2005-07-13
While it may be an incorrect default for you (and me too btw), it's easy to kill it. Thta's what I did with all the latest versions so far, including the zen updater stuff, mono.
But unfortunatelty it keeps re-appearing with KDE updates because openSUSE designates it as a 'suggested' pacakge in one of the kdebase packages, so it keeps getting pulled in by default. It irks me that I have to manually de-select beagle/mono in Yast updates because suggested/recommended packages are brought in automatically, since there is no option to ignore suggested packages vs. required pacakges, or to store package locks etc.
The package dependencies are something that needs to be addressed in openSUSE, a fact that has been acknowledged but is a signficant undertaking given the legacy nature of many of the core packages. Personally I find it ridiculous that the most basic text-based install will bring in Xorg and Gnome dependencies, or that you can't uninstall firefox without breaking Xorg dependencies etc. (And before somebody chimes in, this has nothing to do with rpm vs deb; it's more akin to the meta packages you find in distros like *buntu that can bork your upgrades if removed so effectively force you to settle for default package installations)
The dependency handling is fine for Suse's historic "kitchen sink" approach but they are looking to streamline the installation and offer some much lighter default options, so I imagine we'll see continued improvements in this area as 10.3 progresses.