public inbox for gentoo-releng@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Subject: Re: [gentoo-releng] request for spec files used for building gentoo-install livecd
Date: Sat, 24 Sep 2005 09:16:23 -0400	[thread overview]
Message-ID: <1127567783.12978.11.camel@vertigo.twi-31o2.org> (raw)
In-Reply-To: <20050924065021.75749.qmail@web31806.mail.mud.yahoo.com>

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

On Fri, 2005-09-23 at 23:50 -0700, Ted Kosan wrote:
> Chris indicated that Catalyst had to be heavily modified in order to allow it
> to build the Installer LiveCD which means that the spec files that were used
> were probably only useful with the modified version.

They won't work on the released catalyst version.  One thing that I tend
to do when creating CD images is hard-code things into catalyst to make
it do what I want.  Since I am not distributing this modified catalyst,
there's no "GPL" requirement of any sort.  The main reason I refuse to
release it is because it all is a big, ugly, dirty hack and I'd prefer
people not see such nasty code coming from me... ;]

> My thought is that the Installer spec files are probably useless without the
> modified codebase and if they were released then this would generate a flood of
> distracting questions on the Installer list asking for help on how to get them
> to work.

Correct.

> Anyway, I am also working on a LiveCD that has capabilities that are similar to
> the Installer but I have decided that the best way to do this is to take a
> slower approach, dig into the Catalyst source code and try to fully understand
> all of the pieced needed to achieve this.

This truly is the best method, as we won't bother supporting *anyone*
trying to use gentoo-release-* as livecd/type simply because the release
livecd types *assume* that you're building a Gentoo release and will do
things for you that you may or may not want.  I've created the
generic-livecd livecd/type for others to use.  This type doesn't make
these assumptions and is designed to be more flexible.  Since we don't
use these, our spec files would probably be less than helpful.

> If you are interested in using this approach too we could move this discussion
> over to the catalyst list and continue it there :-)

I look forward to helping you on the catalyst list.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

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

  parent reply	other threads:[~2005-09-24 13:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-23  5:21 [gentoo-releng] request for spec files used for building gentoo-install livecd Mike Rosset
2005-09-23 12:23 ` Chris Gianelloni
2005-09-23 23:45   ` Mike Rosset
2005-09-24  3:40     ` Andrew Gaffney
2005-09-24  6:14       ` Mike Rosset
2005-09-24  6:50         ` Ted Kosan
2005-09-24  7:48           ` Mike Rosset
2005-09-24 13:19             ` Chris Gianelloni
2005-09-24 15:06               ` Mike Rosset
2005-09-24 13:16           ` Chris Gianelloni [this message]
2005-09-26  8:45         ` Paul de Vrieze
2005-09-26 13:42           ` Lance Albertson
2005-09-26 13:50             ` Andrew Gaffney
2005-09-26 13:54             ` Chris Gianelloni
2005-09-26 21:10             ` Mike Rosset

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=1127567783.12978.11.camel@vertigo.twi-31o2.org \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-releng@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