public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joshua Saddler <nightmorph@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Updated handbooks for autobuilds
Date: Tue, 20 Jul 2010 15:54:09 -0700	[thread overview]
Message-ID: <20100720155409.7e884ed4@angelstorm> (raw)
In-Reply-To: <4C4610EE.4060603@gentoo.org>

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

On Tue, 20 Jul 2010 17:11:10 -0400
Richard Freeman <rich0@gentoo.org> wrote:
> Is the process for creating these documented somewhere?  I did some 
> googling and couldn't really find any documentation on how our stages 
> and liveCDs are built in the first place.  There are some generic 
> catalyst docs, but no real docs on how to generate an "official" build - 
> that is one that would be identical (not necessarily bitwise) to what 
> you'd find on the mirrors if they were up to date.

I haven't been able to find a clear step-by-step guide, either. Maybe there's something else in our project space, but I only ever handled the docs side of Releng. Also check the list archives? Supposedly some of the catalyst development is happening on non-Gentoo sites, so maybe there's a bugtracker/wiki/ML upstream. Where's agaffney to answer these questions when ya need him . . .

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2010-07-20 22:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-04 18:42 [gentoo-dev] Updated handbooks for autobuilds Joshua Saddler
2009-10-04 19:28 ` [gentoo-dev] " Christian Faulhammer
2009-10-04 21:11 ` [gentoo-dev] " Joseph Jezak
2009-10-04 21:17 ` Alex Alexander
2010-07-20 20:34 ` Joshua Saddler
2010-07-20 21:11   ` Richard Freeman
2010-07-20 22:54     ` Joshua Saddler [this message]

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=20100720155409.7e884ed4@angelstorm \
    --to=nightmorph@gentoo.org \
    --cc=gentoo-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