public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Kfir Lavi <lavi.kfir@gmail.com>
Subject: Re: [gentoo-dev] How a new ARCH is added to Gentoo?
Date: Mon, 21 Mar 2011 10:14:11 -0400	[thread overview]
Message-ID: <AANLkTi=PM2Yig3b9sVpU=YJF60gh6jxAG0UA-Zk+KKNB@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=XATSV2joaLec=BT=N=Q1Yu8q31GUKn9WvCn1p@mail.gmail.com>

On Mon, Mar 21, 2011 at 8:28 AM, Kfir Lavi wrote:
> Is there any article that elaborate my question?
> My aim is to explain, why Gentoo is much more agile then
> any other binary distribution when hopping between arches.
> Lets say we started development on x86, then we want to
> move to another arch, or a totally new arch. I would like
> to know the process, lets say compared to Debian.

https://bugs.gentoo.org/318251
-mike



  reply	other threads:[~2011-03-21 14:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21 12:28 [gentoo-dev] How a new ARCH is added to Gentoo? Kfir Lavi
2011-03-21 14:14 ` Mike Frysinger [this message]
2011-03-27 12:24   ` Kfir Lavi

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='AANLkTi=PM2Yig3b9sVpU=YJF60gh6jxAG0UA-Zk+KKNB@mail.gmail.com' \
    --to=vapier@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=lavi.kfir@gmail.com \
    /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