Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 151255 - kde-base/kopete-3.5.5-r1 should not depend on kde-base/kdelibs-3.5.5
Summary: kde-base/kopete-3.5.5-r1 should not depend on kde-base/kdelibs-3.5.5
Status: RESOLVED FIXED
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: 2006-10-13 20:10 UTC by Stefan Tittel
Modified: 2006-11-04 01:18 UTC (History)
0 users

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


Attachments
net-im/kopete-3.5.5.ebuild (can mess your system! please read below) (kopete-3.5.5.ebuild,4.29 KB, text/plain)
2006-10-15 09:56 UTC, Matteo Azzali (RETIRED)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Tittel 2006-10-13 20:10:35 UTC
Since recently the net-im/kopete ebuild, which enabled users to use the latest Kopete version even if they didn't use the latest unstable KDE version, has been hard-masked and everybody is designated to use kde-base/kopete now.

Unfortunately the latest Kopete version (kde-base/kopete-3.5.5-r1) depends on kde-base/kdelibs-3.5.5, so after net-im/kopete is gone it's "Use unstable KDE or use outdated Kopete".

I don't think that this is a satisfying situation: Many IM protocols Kopete supports (ICQ, MSN, AIM...) are not open and their implementation is reverse engineered by the Kopete team. Because of this, support for these protocols sometimes becomes unreliable or even breaks completely. This is usually fixed soon with the advent of newer versions, which is why I (as someone who usually prefers using the stable ebuilds) like to have always the latest version of my IM client installed. Unfortunately (after net-im/kopete is gone) in Gentoo this is not possible anymore without upgrading to the latest unstable KDE version.

As long as the latest Kopete version doesn't really need the latest kdelibs (and it seems it doesn't, because the latest Kopete versions always worked fine with the lastest stable kdelibs using the net-im/kopete ebuild), I think this can be resolved by just adjusting the dependencies of kde-base/kopete-3.5.5-r1 so that they are also satisfied by older kdelibs.
Comment 1 Christian Schmitt 2006-10-15 04:57:43 UTC
I totally agree with this. The current situation is unsatisfying and should be changed asap.
Comment 2 Matteo Azzali (RETIRED) gentoo-dev 2006-10-15 09:56:47 UTC
Created attachment 99736 [details]
net-im/kopete-3.5.5.ebuild (can mess your system! please read below)

Unsupported ebuild. Can Mess your system.

Ehm... did you noticed that kopete-0.12.2 ebuild had "need kde-3.4" line ?
I don't think this is possible, however if you really want to try to mess your
system, this is kopete-0.12.2 ebuild "reworked" to get the sources from
kdenetwork-3.5.5 . 
I doubt it can work and I wouldn't mess my system with this, but you're free
to try.

Working on kde-base/kopete-3.5.5 wouldn't change anything but would require 
much more work due to the dependancy of kdelibs "buried" in the kde eclasses.
Comment 3 Diego Elio Pettenò (RETIRED) gentoo-dev 2006-11-02 05:01:16 UTC
This was actually fixed already, kde-base/kopete-3.5.5-r{1,2} does not depend on kdelibs 3.5.5 anymore.
Comment 4 Stefan Tittel 2006-11-04 01:18:25 UTC
Could we make kdenetwork-meta-3.5.2 depend on Kopete versions greater than 3.5.2 and not just 3.5.2? Because at the moment after merging Kopete 3.5.5 the next world update downgrades to 3.5.2 again.

Even adding Kopete 3.5.2 to /etc/portage/package.provided didn't solve the problem for me. Portage still wants to downgrade to 3.5.2 again because of kdenetwork-meta. :(