public inbox for gentoo-releng@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Rosset <schizoid29@gmail.com>
To: gentoo-releng@lists.gentoo.org
Subject: Re: [gentoo-releng] request for spec files used for building gentoo-install livecd
Date: Fri, 23 Sep 2005 16:45:03 -0700	[thread overview]
Message-ID: <2d28d7d9050923164572869626@mail.gmail.com> (raw)
In-Reply-To: <1127478200.24269.91.camel@cgianelloni.nuvox.net>

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

Chris:

Thanks for your reply,

I have enjoyed using Gentoo for many projects over the years, I've also been
very impressed with all of the releng projects. Even more so with
gentoo-installer.

What I thought was a simple request for spec files seems to have turned into

a nightmare. I had Andrew kick me out of "gentoo-installer" for even
bringing it up.

To make matters worst my ideas are not far off of the relengs goals, and
that's really to promote Gentoo and to have an install method that is less
tedious.

So now I'm stuck, I honestly would love to use Gentoo and Catalyst along
with Gentoo-Installer in my project, but how can I if Gentoo is unwilling
pass on information that will allow me to achieve my goals?

Regards,

Michael Rosset


On 9/23/05, Chris Gianelloni <wolf31o2@gentoo.org> wrote:
>
> On Thu, 2005-09-22 at 22:21 -0700, Mike Rosset wrote:
> > I would like to request the spec files used to create the
> > gentoo-install livecd, where every that maybe. I could also use any
> > custom install scripts specific to building the cd since I need to
> > replicate the "gentoo-install" livecd as closely as possible.
>
> Honestly... not gonna happen. At least, not any time soon.
>
> I had to hand-hack catalyst in *many* places along with a several
> hundred-line long fsscript, not to mention the unreleased gli ebuild and
> other such things. Basically, don't expect to see spec files until I
> don't have to manually patch catalyst to get things to work.
>
> Until then, I'd advise joining the gentoo-catalyst mailing list, as this
> isn't really the place for catalyst help/questions. You might also want
> to check out the gentoo-catalyst archives.
>
> --
> Chris Gianelloni
> Release Engineering - Strategic Lead
> Games - Developer
> Gentoo Linux
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (GNU/Linux)
>
> iD8DBQBDM/O4kT4lNIS36YERAkYNAKCIXzuNZrkFS1CiywPUu/SUK28JMwCgnZLH
> ERMFZNGEROSOmXfsvSqV4wQ=
> =lGog
> -----END PGP SIGNATURE-----
>
>
>

[-- Attachment #2: Type: text/html, Size: 2486 bytes --]

  reply	other threads:[~2005-09-23 23:45 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 [this message]
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
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=2d28d7d9050923164572869626@mail.gmail.com \
    --to=schizoid29@gmail.com \
    --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