From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] kde update
Date: Tue, 31 May 2011 08:27:19 -0700 [thread overview]
Message-ID: <BANLkTi=FAHc72Ze6Ngyt9bJGLQK_0eQkSA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikh4QWB9AiHLbvz+TTs4P+dih8DCg@mail.gmail.com>
On Tue, May 31, 2011 at 8:11 AM, Paul Hartman
<paul.hartman+gentoo@gmail.com> wrote:
> On Mon, May 30, 2011 at 11:45 AM, Alain DIDIERJEAN
> <alain.didierjean@free.fr> wrote:
>> Trying to update from kde4.5 to kde4.6
>
> I find that it is easier to unmerge old version :4.5 KDE, then emerge
> the new version :4.6. Upgrade always seems to be a mess like that.
>
Probably there's no real problem but I think in my recent machines if
I've chosen the KDE profile and try something like emerge -Cp kde-meta
then there are lots of warning messages about how I'm removing parts
of @system. It's unlikely (in my mind anyway) that anything would be
removed that stops one from doing the 4.6 emerge, but if one goes this
way they should look very carefully at what's getting taken out just
to make sure.
Cheers,
Mark
next prev parent reply other threads:[~2011-05-31 15:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 16:45 [gentoo-user] kde update Alain DIDIERJEAN
2011-05-30 17:16 ` Mick
2011-05-30 19:02 ` Neil Bothwick
2011-05-30 19:11 ` Mick
2011-05-30 20:04 ` Dale
2011-05-31 15:11 ` Paul Hartman
2011-05-31 15:27 ` Mark Knecht [this message]
2011-05-31 19:07 ` Alan McKinnon
2011-05-31 20:00 ` Dale
2011-05-31 20:20 ` Nils Larsson
2011-05-31 21:13 ` Dale
2011-05-31 21:32 ` Alan McKinnon
2011-05-31 21:55 ` Dale
2011-05-31 22:02 ` Alan McKinnon
2011-05-31 22:35 ` Dale
2011-05-31 23:30 ` Alan McKinnon
2011-05-31 23:49 ` Peter Humphrey
2011-06-01 0:11 ` Dale
2011-05-31 20:35 ` Alan McKinnon
2011-06-02 14:32 ` [gentoo-user] kde update: SOLVED Alain DIDIERJEAN
2011-06-02 15:44 ` Mick
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='BANLkTi=FAHc72Ze6Ngyt9bJGLQK_0eQkSA@mail.gmail.com' \
--to=markknecht@gmail.com \
--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