From: Jonathan Callen <abcd@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: kde4 upgrading
Date: Wed, 28 Oct 2009 00:37:02 -0400 [thread overview]
Message-ID: <4AE7CA6E.1010701@gentoo.org> (raw)
In-Reply-To: <loom.20091028T010741-743@post.gmane.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
James wrote:
> kde-meta is ideal for me. I thought it was going away?
> Since kde(4)-meta is alive and well, that is my preferred
> method. I hope when kde-meta goes away (?) there is a migration
> plan? When this whole kde4 venture started for me (feb 09)
> I was told to avoid meta as it is going away.......
>
> [...]
>
> How long is kde-meta going to be around?
> That's really what I'm looking for.....
>
kde-base/kde*-meta won't be going away any time soon, if at all. The
original plan, way back when, was to transition everything to sets, but
the current implementation in portage 2.2_rc* does not currently do
everything that is needed, so we are recommending the usage of the meta
packages.
- --
Jonathan Callen
Gentoo KDE Developer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.13 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkrnym4ACgkQOypDUo0oQOo9ZQCbBwM1fUMQzv+mReF/aaEkr8I7
LLUAmgIaNDiixVl5fd+PQY2OjqMPY1pU
=icEh
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2009-10-28 4:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 16:13 [gentoo-user] kde4 upgrading James
2009-10-27 22:24 ` Alan McKinnon
2009-10-27 22:47 ` Frank Steinmetzger
2009-10-28 0:30 ` [gentoo-user] " James
2009-10-27 23:54 ` [gentoo-user] " Neil Bothwick
2009-10-28 0:28 ` [gentoo-user] " James
2009-10-28 4:37 ` Jonathan Callen [this message]
2009-10-28 8:58 ` Alan McKinnon
2009-10-28 13:44 ` Stroller
2009-10-29 14:59 ` [gentoo-user] Re (DONE): " James
2009-10-29 17:53 ` Stroller
2009-10-29 19:17 ` Alan McKinnon
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=4AE7CA6E.1010701@gentoo.org \
--to=abcd@gentoo.org \
--cc=gentoo-user@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