public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alex Schuster <wonko@wonkology.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] --buildpkg and doing a dry run on a upgrade
Date: Sat, 21 Aug 2010 13:42:32 +0200	[thread overview]
Message-ID: <201008211342.35140.wonko@wonkology.org> (raw)
In-Reply-To: <4C6FB126.4020708@gmail.com>

Dale writes:

> 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.

I'm no guru, but I'm very sure it won't work.

You could do this on a second machine, or in a chroot, or in a virtual 
machine, and then distribute the binary packages. Which would be quite 
some additional work.

I'm running KDe 4.5, and it works fine. That is, there are fewer new bugs 
for me than were fixed.

	Wonko



  reply	other threads:[~2010-08-21 11:43 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 [this message]
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

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=201008211342.35140.wonko@wonkology.org \
    --to=wonko@wonkology.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