Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 233705 - konqueror in kde 4.1 should depend on dolphin
Summary: konqueror in kde 4.1 should depend on dolphin
Status: VERIFIED CANTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-02 13:44 UTC by Alexander Romanenko
Modified: 2009-12-07 18:59 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Romanenko 2008-08-02 13:44:42 UTC
When one completes emerge of konqueror 4.1 he would expect it to work but it does not, unless dolphin is also emerged.
In 3.x konqueror had its own service for directory browsing: konq_iconview.  In 4.1 it uses dolphinpart, which appears only after emerging dolphin: without it konqueror is useless.  Therefore, i think there should be a dependency of konqueror on dolphin.

Reproducible: Always

Steps to Reproduce:
1.emerge konqueror on a minimal kde4.1
2.open konqueror and try to browse a directory.

Actual Results:  
Erro: You have associated Konqueror with inode/directory, but it cannot handle this file type

Expected Results:  
Ability to browse directories
Comment 1 Alex Boag-Munroe 2008-08-02 14:55:47 UTC
Perhaps instead of it having dolphin as a dependency, have a USE flag if you want to enable konqueror as a file manager?
Comment 2 Jorge Manuel B. S. Vicetto Gentoo Infrastructure gentoo-dev 2008-08-03 14:16:41 UTC
This is a common source of bug reports. Optional run-time deps don't need to be defined in RDEPEND and it has been our policy not to add use flags for them.
Also, the kde team has yet to provide ebuilds for kde-4.1, so we can't fix what we haven't provided.
Comment 3 Alexander Romanenko 2008-08-03 14:56:38 UTC
>> Optional run-time deps don't need to be
defined
Well, thats the problem.  Konqueror is first of all a file manager. Browsing directories is not really an optional feature: thats what it was designed to do and thats what users expect it to do. Having it always opening with an error message that most will not understand is not a good idea, i think. This is not like not having no GIF support problem that i had which i solved by adding a GIF flag.  That was, indeed, an optional feature: to view gif or not to view gifs. But konqueror browsing directories is its core functionality and should not be made an option.  Thats just my opinion.

I do understand the issue of optional run-time and i do believe gentoo's phylosophy about it is correct, which is why i chose the distribution in this first place, but this one particular issue i think could be looked at.

>>the kde team has yet to provide ebuilds
Thats why i thought this is the right time to bring this up to see if issues like this will not hinder the real release.

Thanks for responding.
Comment 4 Jorge Manuel B. S. Vicetto Gentoo Infrastructure gentoo-dev 2008-08-03 15:14:29 UTC
KDE devs seem to disagree. I understand their split of konqueror in konqueror and dolphin to send a clear message:
konqueror - web browser
dolphin - file manager
Comment 5 Alexander Romanenko 2008-08-03 15:26:58 UTC
Interesting.
Well thanks for clearing it up.
Comment 6 Luke Wilson-Stepan 2009-11-22 21:56:53 UTC
There should at least be an eselect news entry for this.  I had to do a lot of searching to figure out why filebrowsing was broken in kde4's konqueror.  That's one of the things I expect it to do, and most kde users will agree with me.
Comment 7 Romain Perier (RETIRED) gentoo-dev 2009-11-22 22:11:36 UTC
(In reply to comment #6)
> There should at least be an eselect news entry for this.  I had to do a lot of
> searching to figure out why filebrowsing was broken in kde4's konqueror. 
> That's one of the things I expect it to do, and most kde users will agree with
> me.

Jorge: it would be nice to be talk about that in the documentation nop ? (except if it's already done...)
However, KDE4 is out since a while now... so... what do you think ?
Comment 8 Jorge Manuel B. S. Vicetto Gentoo Infrastructure gentoo-dev 2009-11-23 01:38:53 UTC
I talked earlier with Tomas about documenting some of our "options" in our docs. This is another case we could document.
In any case, note the following was added to konqueror a *long* time ago:

elog "If you want to use konqueror as a filemanager, install the dolphin kpart:"
elog "emerge -1 kde-base/dolphin:${SLOT}"
Comment 9 Lambert Carsten 2009-12-07 17:00:09 UTC
(In reply to comment #4)
> KDE devs seem to disagree. I understand their split of konqueror in konqueror
> and dolphin to send a clear message:
> konqueror - web browser
> dolphin - file manager
> 

So what should I have been using as a filemanager all these years when I was running kde instead of the 'Konqueror web browser'?

If something changes the users should be informed other than by just letting them google for an answer after an emerge breaks something. I have been with gentoo a long time but the message I am getting lately is that users are not appreciated.
This is the wrong way of 'communicating' changes to users.
Comment 10 Samuli Suominen (RETIRED) gentoo-dev 2009-12-07 17:21:41 UTC
(In reply to comment #9)
> This is the wrong way of 'communicating' changes to users.

Which way is that? As Jorge already explained in Comment #8 there is a message from Portage after Konqueror install that you need to install Dolphin. 

What more would you need?! IMHO, the message is a overkill as is. ;-)
Comment 11 Lambert Carsten 2009-12-07 18:59:14 UTC
> Which way is that? As Jorge already explained in Comment #8 there is a message
> from Portage after Konqueror install that you need to install Dolphin. 
> 
> What more would you need?! IMHO, the message is a overkill as is. ;-)

Granted the message is there (amongst a long list of other messages including the packages that failed because amongst other lafilefixer wasn't used etc.)

My point is I had a working filemanager before the 'upgrade' (kde3.5 to kde4) and after resolving all the problems portage spit out I did not have a filemanager (and a whole lot of other issues as a bonus).

The upgrade from kde3.5 to kde4 probably needed to be handled differently given the issues with kde4. However that is easy to say when I am not the one doing the work. :)

I am not looking for a discussion. As a user I thought it was time to return some feedback on one point after a long list of problems I have been getting with 'updates' the past year. I never even wanted to move to kde4 and now I know why. But portage was breaking my (kde)desktop system if I didn't oblige. So I will be returning to a backup system and forget about updating for a while. My next real upgrade will probably take me away from Gentoo I am sad to say. (Gentoo has been on most of my systems for many years.)