public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Anthony Dodson <ADodson@Lumenos.com>
To: "Gentoo-Portage-Dev (E-mail)" <gentoo-portage-dev@lists.gentoo.org>
Subject: [gentoo-portage-dev] cloning systems across architectures
Date: Wed, 10 Mar 2004 15:44:14 -0500	[thread overview]
Message-ID: <3592E70770A47748BE84101253BACC79125DCB@lumex02.lumenos.com> (raw)

Sorry if this is the wrong list for this question.

If I build a system, optimized for the architecture without room for
backwards compatibility, containing all the software I want, what's an easy
way to "clone" that build onto another machine with a different
architecture?

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?

(Sounds like Tal Peer's GLEP 21 proposal might just solve this, but how
could it be done now?)

Thanks,
Anthony Dodson

IMPORTANT WARNING: 
This e-mail is intended for the use of the person to whom it is addressed
and may contain information that is privileged and confidential, the
disclosure of which is governed by applicable law. Dissemination,
distribution or copying of this information in an unauthorized manner is
strictly prohibited. Sender accepts no liability for any damage caused by
any virus transmitted by this e-mail. If you receive this in error, please
notify the sender. 


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


             reply	other threads:[~2004-03-10 20:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-10 20:44 Anthony Dodson [this message]
2004-03-10 22:02 ` [gentoo-portage-dev] cloning systems across architectures Pieter Van den Abeele
2004-03-10 23:25 ` George Shapovalov
2004-03-11  1:46   ` Jason Stubbs
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=3592E70770A47748BE84101253BACC79125DCB@lumex02.lumenos.com \
    --to=adodson@lumenos.com \
    --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