From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] --buildpkg and doing a dry run on a upgrade
Date: Sat, 21 Aug 2010 22:37:15 +0200 [thread overview]
Message-ID: <201008212237.15870.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <4C70349B.1030302@gmail.com>
Apparently, though unproven, at 22:18 on Saturday 21 August 2010, Dale did
opine thusly:
> > Here's excellent advice:
> >
> > Do not install KDE-4.5 yet
> >
> > wait for 4.5.1
> >
> > First, it's in an overlay, so when 4.5 hits the tree you will unmerge the
> > whole lot again and redo it. How many spare cycles you got?
> >
> > If you have 4.4.5 installed from portage you will likely hit clashes with
> > the overlay. There's were never pleasant in the 4.[23] era, I don't see
> > that changing.
> >
> > 4.5.0 has some pretty severe regressions, bad enough for QA to not put it
> > in the tree
> >
> > 4.5.0 does not have the kdepim suite - this might not apply to you. I can
> > just imagine the akonadi updates when 4.5.1 hits the tree....
> >
> > You gotta ask yourself "Is there a COMPELLING need for 4.5.0 other than
> > it's brand new and shiny?"
>
> I did some googlin last night and ran across some blog. I think it was
> on KDE's website but anyway. The blog said about the same thing you
> said. It appears to be a . . . . mess. ;-)
>
> Any idea when 4.5.1 will be in the tree even if masked/keyworded?
You can expect 4.5.1 to be released by KDE about a month after 4.5.0.
If it goes into the tree that will take about 3 days or so.
--
alan dot mckinnon at gmail dot com
prev parent reply other threads:[~2010-08-21 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 10:57 [gentoo-user] --buildpkg and doing a dry run on a upgrade Dale
2010-08-21 11:42 ` Alex Schuster
2010-08-21 11:52 ` Dale
2010-08-21 12:01 ` Alan McKinnon
2010-08-21 20:18 ` Dale
2010-08-21 20:37 ` Alan McKinnon [this message]
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=201008212237.15870.alan.mckinnon@gmail.com \
--to=alan.mckinnon@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