From: Chris Bainbridge <C.J.Bainbridge@ed.ac.uk>
To: Gentoo Dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] creating stage files
Date: Thu, 20 Nov 2003 11:32:22 +0000 [thread overview]
Message-ID: <200311201132.22136.C.J.Bainbridge@ed.ac.uk> (raw)
In-Reply-To: <3FBC2C0B.8010003@mcve.com>
On Thursday 20 November 2003 02:50, Brad House wrote:
> besides 'stager' or 'catalyst' ??
>
> Andrew Gaffney wrote:
> > I was wondering what the procedure was for creating stage tarballs for
> > the different architectures? I'm wondering because I'm trying to create
> > a system image for my Dreamcast (yes, I know this is embedded territory
> > but humor me) and I want to try a few different approaches.
Which one is better? Is there an ebuild for catalyst (emerge -S/s doesn't find
one), or any documentation apart from the brief page at http://
www.gentoo.org/proj/en/releng/catalyst/index.xml ?
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-11-20 11:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 2:45 [gentoo-dev] creating stage files Andrew Gaffney
2003-11-20 2:50 ` Brad House
2003-11-20 5:24 ` Andrew Gaffney
2003-11-20 11:32 ` Chris Bainbridge [this message]
2003-11-20 18:08 ` Eric Olinger
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=200311201132.22136.C.J.Bainbridge@ed.ac.uk \
--to=c.j.bainbridge@ed.ac.uk \
--cc=gentoo-dev@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