public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ian Clowes" <clowes_ian@hotmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Is binary emerge equivalent to source emerge?
Date: Wed, 07 Sep 2005 18:45:41 +0000	[thread overview]
Message-ID: <BAY103-F385D09A4A40DB61ED2E2E1F7A60@phx.gbl> (raw)

Hi

I've been building a box for a specific purpose by emerge-ing and playing 
with various packages until I ended up with something that matched what I 
wanted.

I'd now like to rebuild the box including just the packages that turned out 
to be relevant.

Rather than do source installs again I was thinking of using the current box 
to build binary packages before wiping it and doing a rebuild from these 
binaries, hence saving on heaps of build time after setting make.conf, etc. 
to match the current install.  One additional step that I think is important 
is to use a Portage snapshot from the current machine.

A few questions...

1) Does this seem like a sensible idea?  Will it generally work?
2) Will --usepkg --getbinpkg use binary packages for dependencies?
3) Is the resultant Portage database equivalent to source emerges, 
especially in respect of future --updates, --newuse, etc?
4) Am I right to use a Portage snapshot from the current machine?
5) Is this idea so close to the Catalyst idea that I should use its methods 
to achieve my aims?

TIA
IanC


-- 
gentoo-user@gentoo.org mailing list



             reply	other threads:[~2005-09-07 19:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-07 18:45 Ian Clowes [this message]
2005-09-07 21:39 ` [gentoo-user] Is binary emerge equivalent to source emerge? Sascha Lucas
2005-09-07 20:38   ` Zac Medico
2005-09-07 23:07     ` Sascha Lucas
2005-09-07 22:56       ` Zac Medico
2005-09-08 14:04         ` Sascha Lucas

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=BAY103-F385D09A4A40DB61ED2E2E1F7A60@phx.gbl \
    --to=clowes_ian@hotmail.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