public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] small distros - setups and practices?
Date: Thu, 01 May 2008 10:04:26 -0700	[thread overview]
Message-ID: <1209661466.7206.637.camel@cgianelloni.quova.com> (raw)
In-Reply-To: <20080423020310.GA6373@dev.local>

[-- Attachment #1: Type: text/plain, Size: 720 bytes --]

On Wed, 2008-04-23 at 10:03 +0800, Max Arnold wrote:
> > > I want special build host, where all binary targets are built. Its setup
> > > should be easily repeatable by other developers (i.e. every task should be scripted,
> > > without manual tweaks like 'chroot here and patch/emerge this'). Catalyst with
> > > specs and overlays seems fine to me.
> > 
> > Sure.  In fact, I have 2 different "host types" right now, a "master"
> > and a "build host" though they can reside on the same machine.
> 
> Which roles they have?

I'm not sure that I follow.  Are you asking what specific tasks would be
performed by the roles above?

-- 
Chris Gianelloni
Release Engineering Strategic Lead
Games Developer

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-05-01 17:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-22 12:18 [gentoo-catalyst] small distros - setups and practices? Max Arnold
2008-04-22 16:58 ` Chris Gianelloni
2008-04-23  2:03   ` Max Arnold
2008-05-01 17:04     ` Chris Gianelloni [this message]
2008-05-02  2:20       ` Max Arnold
2008-05-02 15:03         ` Chris Gianelloni
2008-05-02 15:42           ` Max Arnold
2008-05-05 18:02             ` Robert Šmol
2008-05-07  6:45               ` Chris Gianelloni
2008-05-05 19:41           ` Ramon van Alteren
2008-05-07  6:46             ` Chris Gianelloni
2008-05-09 10:02               ` Ramon van Alteren
2008-07-22  4:37                 ` John Eckhart

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=1209661466.7206.637.camel@cgianelloni.quova.com \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-catalyst@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