Do we really need both of these ebuilds? For people using the meta-ebuilds, such as myself, its a pain to have to add kopete to package.provided, and also, have all the files chucked into /usr/ rather than /usr/kde which would seem to make more sense.
Yes we do.
I'm sure I'm not the only one that would appreciate some elaboration on that answer. I've been wondering about this situation, as well. I did some searching but was unable to find documentation about the background that gives us this strange situation (I'm not saying it doesn't exist - I just couldn't find it).
(In reply to comment #2) > I'm sure I'm not the only one that would appreciate some elaboration > on that answer. I've been wondering about this situation, as well. > I did some searching but was unable to find documentation about > the background that gives us this strange situation (I'm not saying > it doesn't exist - I just couldn't find it). > From the first entry of the net-im/kopete changelog (/usr/portage/net-im/kopete/ChangeLog): "Add kopete 0.12_alpha1, released outside KDE's release cycle. Masked as it's still an alpha release; blocks kde-base/kopete." :) So if you don't need the possible new features/modifications which are still not in the version of Kopete, bundled with KDE, you should probably stick with kde-base/kopete. (In reply to comment #0) > Do we really need both of these ebuilds? > For people using the meta-ebuilds, such as myself, its a pain to > have to add kopete to package.provided, and also, have all the files > chucked into /usr/ rather than /usr/kde which would seem to make > more sense. > Do you need the possible new features/modifications which are still not in the version of Kopete, bundled with KDE? If no, just unmerge net-im/kopete and emerge kde-base/kopete (and remove the entry in package.provided). If yes, kdenetwork-meta now depends on either kde-base/kopete, or net-im/kopete, so you should not need to add it to your package.provided configuration file anymore (modifications done on 2006-03-07, by Diego, a few weeks after having introduced net-im/kopete, but I guess you were still using KDE 3.5.1 -not the r1 version-, at the time of your report). Anyway, about the existence of two packages for Kopete, here is some examples of user documentation which might be useful (in pkg_postinst() of Kopete ebuilds): - in net-im/kopete: ewarn ewarn "The net-im/kopete package you just emerged is released" ewarn "outside of the KDE release cycle. As such, it might be" ewarn "less tested, but might contain new features and" ewarn "modifications not yet in the official kde-base/kopete" ewarn "package, part of KDE." ewarn ewarn "If you do not need the newest versions of Kopete," ewarn "you should probably unmerge net-im/kopete, and" ewarn "emerge kde-base/kopete instead." ewarn - in kde-base/kopete: einfo einfo "The kde-base/kopete package you just emerged is released" einfo "as part of the official KDE release cycle. If you need" einfo "a newer version (maybe for some new feature or" einfo "modification), you might try to unmerge kde-base/kopete," einfo "and emerge net-im/kopete instead (note, however, that not" einfo "being part of the KDE release cycle, the net-im/kopete" einfo "package might be less tested)." einfo (Well, for kde-base/kopete-3.5.2, there is already a message about net-im/kopete, so the above message should probably only be included in the following versions.)
*** Bug 146685 has been marked as a duplicate of this bug. ***
