Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-releng
Navigation:
Lists: gentoo-releng: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-releng@g.o
From: Jason Wever <weeve@g.o>
Subject: Re: Livecd building with catalyst
Date: Tue, 16 Dec 2003 18:40:03 -0500
On Tue, 16 Dec 2003 13:33:33 -0500
John Davis <zhen@g.o> wrote:

> As arch leads, don't be concerned with livecds and stages at this point.
> What you need to be concerned about is getting your arch tree ready for
> release and meeting deadline. Releng will take care of making sure that
> livecd generation is functional and complete before the release date
> comes. When catalyst is ready, releng will inform everyone on what they
> need to do to get stages rolled and livecds created - believe me, both
> will not be nearly as tedious or time consuming as they were previously.

As an arch lead, I'm expecting you'll be coming to me for help building
the LiveCD as each arch has it's own bootloader and quirks.  

In regards to preparing the tree, can we get a list of what will be in the
upcoming GRP package set?

-- 
Jason Wever
Gentoo/Sparc Team Co-Lead
Attachment:
pgpYKzVIyAurk.pgp (PGP signature)
Replies:
Re: Livecd building with catalyst
-- John Davis
Re: Livecd building with catalyst
-- Daniel Robbins
References:
Livecd building with catalyst
-- Guy Martin
Re: Livecd building with catalyst
-- Jason Wever
Re: Livecd building with catalyst
-- John Davis
Navigation:
Lists: gentoo-releng: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Livecd building with catalyst
Next by thread:
Re: Livecd building with catalyst
Previous by date:
Re: [gentoo-core] releng boxes
Next by date:
Re: Livecd building with catalyst


Updated Jun 17, 2009

Summary: Archive of the gentoo-releng mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.