From: Dale <rdalek1967@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 15:18:35 -0500 [thread overview]
Message-ID: <4C70349B.1030302@gmail.com> (raw)
In-Reply-To: <201008211401.52130.alan.mckinnon@gmail.com>
Alan McKinnon wrote:
> Apparently, though unproven, at 12:57 on Saturday 21 August 2010, Dale did
> opine thusly:
>
>
>> Hi,
>>
>> I'm wanting to install the latest KDE 4.5 which is in the kde overlay.
>> I got everything unmasked, keyworded and ready to go. Since this is a
>> large upgrade and will take some time to compile, I would like to just
>> build the binaries then come back and install them when the compiling is
>> all done. The emerge man page says this:
>>
>> --buildpkgonly (-B)
>> Creates binary packages for all ebuilds processed without actually
>> merging the packages. This comes with the caveat that all build-time
>> dependencies must already be emerged on the system.
>>
>> The part that I have a question on is the dependencies. Will portage be
>> able to build all the packages when the previous packages are not
>> installed yet? My thinking says this won't work but looking for a
>> second opinion from a more "seasoned" guru.
>>
>
> 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?
Dale
:-) :-)
< Dale is going to remove the overlay now >
next prev parent reply other threads:[~2010-08-21 20:19 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 [this message]
2010-08-21 20:37 ` 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=4C70349B.1030302@gmail.com \
--to=rdalek1967@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