From: "Michael Weyershäuser" <thedude0001@gmx.de>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites for net-im/kopete
Date: Fri, 27 Oct 2006 15:43:56 +0200 [thread overview]
Message-ID: <45420D1C.8020901@gmx.de> (raw)
In-Reply-To: <200610121226.59991@enterprise.flameeyes.is-a-geek.org>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
Diego 'Flameeyes' Pettenò schrieb:
> As per summary, net-im/kopete is going away (again).
> For a while upstrem released some versions out of the KDE release cycle
> (0.12_alpha through 0.12.2), but now 0.12.3 was merged again inside
> kdenetwork-3.5.5, so the point of having it in net-im is gone again.
>
> As I've heard the most foolish requests about this, I'll be masking it for
> good. kde-base/kopete has already all the changes I did to net-im/kopete in
> the past months backported, so there's no regression in moving to it now.
>
A user just brought one reason to my attention why it might be a good
idea to keep this around separate from kdenetwork:
kde-base/kopete-3.5.5 depends on the whole KDE installation being 3.5.5,
while users who run stable may want to have their stable KDE
installation and only kopete ~amd64. kde-base/kopete-3.5.5 depends on
kdelibs-3.5.5 which in turn means your whole KDE installation has to be
3.5.5, while the current net-im/kopete may also be installed with older
KDE versions.
Not sure if this is a good enough reason to keep the package in portage,
but it's something that should be taken into consideration for those
running a stable gentoo...
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2006-10-27 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 10:26 [gentoo-dev] Last rites for net-im/kopete Diego 'Flameeyes' Pettenò
2006-10-27 13:43 ` Michael Weyershäuser [this message]
2006-10-27 13:55 ` Diego 'Flameeyes' Pettenò
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45420D1C.8020901@gmx.de \
--to=thedude0001@gmx.de \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox