public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jason Stubbs <jstubbs@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] cloning systems across architectures
Date: Thu, 11 Mar 2004 10:46:55 +0900	[thread overview]
Message-ID: <200403111046.55363.jstubbs@gentoo.org> (raw)
In-Reply-To: <200403101525.51119.george@gentoo.org>

On Thursday 11 March 2004 08:25, George Shapovalov wrote:
> On Wednesday 10 March 2004 12:44, Anthony Dodson wrote:
> > For instance, how can one move the definition of the "world" class to the
> > new machine (bootstrapped) and then emerge all that software at once?  Is
> > there a better approach?
>
> So, you basically have two different systems and you want to optimize both
> (so no common denominator) or they are different arches,  meaning that you
> would rather recompile; but you would rather not mess with all the
> individual packages? Is this the situation?
> Then yes, no need to go package by package:
> 1. clone your /etc/make.conf and adjust C[XX]FLAGS correspondingly (but
> keep USE definition identical)
> 2. copy /var/cache/edb/world over
    (to a different directory)
> 3. do "emerge -[p]e world" or even simply "emerge world"
    emerge $(cat world)

Emerge now checks to see if a package listed in the world file is installed 
before doing anything with it. If it's not installed, it is skipped.

Regards,
Jason Stubbs

--
gentoo-portage-dev@gentoo.org mailing list


  reply	other threads:[~2004-03-11  1:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-10 20:44 [gentoo-portage-dev] cloning systems across architectures Anthony Dodson
2004-03-10 22:02 ` Pieter Van den Abeele
2004-03-10 23:25 ` George Shapovalov
2004-03-11  1:46   ` Jason Stubbs [this message]
2004-03-11 15:03     ` Drake Wyrm

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=200403111046.55363.jstubbs@gentoo.org \
    --to=jstubbs@gentoo.org \
    --cc=gentoo-portage-dev@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