Bug 5357 - Default-kde4-config requires plasma-applet-icontasks
Summary: Default-kde4-config requires plasma-applet-icontasks
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 3342
  Show dependency treegraph
 
Reported: 2012-04-11 19:49 CEST by David Walser
Modified: 2012-05-15 14:10 CEST (History)
5 users (show)

See Also:
Source RPM: mageia-kde4-config-2-0.20120411.3.mga2.src.rpm
CVE:
Status comment:


Attachments

Description David Walser 2012-04-11 19:49:01 CEST
If you have any KDE apps installed at all, they require libkdecore5.  libkdecore5 requires kde4-config-file.  The default package installed to satisfy that virtual require is Default-kde4-config.  If you have a Mageia 1 installation with any KDE program, you will have that package installed.  If you have KDM installed especially, you will have that package installed (and it's also the one that provides the most normal KDM configuration).

If you upgrade to Mageia 2, when Default-kde4-config is upgraded, the new require of "plasma-applet-icontasks" will pull in requires of kdebase4-workspace as well as a whole bunch of other stuff.  This adds a lot in terms of disk space requirements, and it also adds a KDE desktop as a login option, which you may not want to have.  I know that you could switch to vanilla-kde4-config (with its weird KDM configuration) and get rid of these additional requires, but you shouldn't have to do that, and if you're upgrading a VM with a small disk, the damage may already be done anyway.

Requires like these should not be added to the config package (and remember, it's required by anything that requires libkdecore5).  plasma-applet-icontasks probably shouldn't be required by anything at all, if anything it should be a suggests somewhere, but even then it should be on a package that actually uses it (kdebase4-workspace or task-kde4 would be better options).
David Walser 2012-04-11 19:49:29 CEST

CC: (none) => balcaen.john

David Walser 2012-04-11 19:49:44 CEST

CC: (none) => juan.baptiste

David Walser 2012-04-11 19:49:55 CEST

CC: (none) => lmenut

David Walser 2012-04-11 19:50:18 CEST

CC: (none) => dmorganec

David Walser 2012-04-11 19:57:00 CEST

Blocks: (none) => 3342

Comment 1 John Balcaen 2012-04-11 20:03:07 CEST
the default configuration use plasma-applet-icontasks.
If you find a better solution to ensure that plasma-applet-icontasks is installed when Default-kde4 is used i'll (or lmenut/juancho) be pleased to implement it.
Adding the require on kde-workspace is wrong since workspace does not need it at all to work, & task-kde4 does not ensure it's available.
Comment 2 John Balcaen 2012-04-11 20:08:38 CEST
& vanilla is just the upstream config.
A workaround would to use rpmstrate for this eventually but it won't prevent breakage by end users.
Luc, Ennael ? any idea on this ?

CC: (none) => ennael1

Comment 3 David Walser 2012-04-11 20:14:06 CEST
(In reply to comment #1)
> the default configuration use plasma-applet-icontasks.

The default *workspace* configuration uses it.  It is not needed by every individual KDE application.

> If you find a better solution to ensure that plasma-applet-icontasks is
> installed when Default-kde4 is used i'll (or lmenut/juancho) be pleased to
> implement it.

Moving the requires/suggests to something that actually uses it would be better.

> Adding the require on kde-workspace is wrong since workspace does not need it
> at all to work, & task-kde4 does not ensure it's available.

It would be better to have something that actually uses it require it (or suggest it, which would install it by default anyway), rather than having it required by anything that uses KDE libraries.

rpmsrate would work for new installations, suggests would pull it in for everyone, even for upgrades (unless they explicitly did a urpmi --no-suggests upgrade), but again, it should be pulled in by what actually uses it (the workspace), rather than anything that uses the KDE libraries at all.
Comment 4 John Balcaen 2012-04-11 20:31:46 CEST
So you suggest to splitted more the default config ?
Comment 5 David Walser 2012-04-11 20:40:01 CEST
(In reply to comment #4)
> So you suggest to splitted more the default config ?

Maybe, maybe not.  Here are two thoughts on this:

Is there something in this package this *is* needed by every program that uses the KDE libraries?  If not, libkdecore5 shouldn't require it, and that would solve some problems.  If so, then yes, maybe the package could be split into things that are required by anything using the KDE libraries in one package, and workspace configuration into another package.

My other thought is, even if you leave everything in one config package, who cares if you have workspace configuration installed with no workspace installed?  It's just config files, they're not hurting anything by being there.  If the workspace is installed it will use them, if not, nothing will.

What's really wrong here, is that rather than having the workspace require its configuration, the configuration files are requiring the workspace.  Basically, that's backwards.
Comment 6 David Walser 2012-04-24 20:18:04 CEST
I just did another upgrade test; here's the current status.

Upgrading installed kdebase4-workspace, which is bad.

urpme kdebase4-workspace didn't say it would remove ark and konsole, which is good.

urpme kdebase4-workspace did force removal of kdm still, which is bad.

Installing vanilla-kde4-config allowed me to remove kdebase4-workspace without removing kdm, which is good.

Installing vanilla-kde4-config installed a bunch of additional plasma applets, which is bad.

So, not totally solved yet, but there's been some progress.
Comment 7 David Walser 2012-04-24 20:21:09 CEST
Not really related to this bug, but I just logged into the kdebase4-workspace that was installed, and the DPMSControl error message that used to pop up at the top during login that I mentioned to you on mageia-dev no longer appears, so that's an improvement.

Also, this may seem counterintuitive considering this bug, but if you're going to have the workspace pulling things in, it should pull in the Show Desktop widget, since it's used in the default configuration.  Right now I just have a red X there because that widget is missing (this isn't a new problem).
Comment 8 David Walser 2012-04-24 20:35:49 CEST
I should mention that KDM with the vanilla config looks nicer than it did before.
Comment 9 Luc Menut 2012-04-25 00:45:23 CEST
(In reply to comment #5)
[...]
> If not, libkdecore5 shouldn't require it, and that would
> solve some problems.

since kdelibs4-4.8.2-3.mga2, libkdecore5 requires only mageia-kde4-config-common, so that individual kde apps used with another DE than KDE, don't require kde4-config-file and workspace components.


(In reply to comment #6)
[...]
> 
> urpme kdebase4-workspace did force removal of kdm still, which is bad.

kdm needs some config files that are currently provided by kde4-config-file.
Personnaly, I don't plan to change this for mga 2. It's too risky so late.

[...]

> Installing vanilla-kde4-config installed a bunch of additional plasma applets,
> which is bad.

These plasma applets are only suggested, so you can easily avoid their install, or remove them.
urpmq --suggests vanilla-kde4-config
kde-wallpapers
plasma-applet-frame
plasma-applet-news
plasma-applet-weather
plasma-applet-opendesktop
plasma-applet-knowledgebase
Comment 10 Manuel Hiebel 2012-05-15 13:55:08 CEST
any news ?
Comment 11 John Balcaen 2012-05-15 14:10:34 CEST
I'll mark it as fixed since the last change made by luc ( libkdecore requires only the common configuration files so it does not pull icontasks. )

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.