From: Pieter Van den Abeele <pvdabeel@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Cc: klieber@gentoo.org
Subject: Re: [gentoo-releng] x86 (ppc?) cd layout for 2004.0
Date: Wed, 18 Feb 2004 15:08:28 +0100 [thread overview]
Message-ID: <EC9EFD8F-621B-11D8-8B24-0003938E7E46@gentoo.org> (raw)
In-Reply-To: <1077090774.6674.281.camel@wave.gentoo.org>
Hi,
On 18 Feb 2004, at 08:52, Daniel Robbins wrote:
> Likewise, if this is adopted for PPC, it would allow us to have
> potentially 1 instead of 3 (or maybe even 4?) disc 1's, and reduce our
> mirror load by an additional 900MB to 1.4GB. It would also give ppc
> users one CD1 to download that provides them with pre-built stage3's
> for
> ppc, g3, g4 (32-bit g5?) which I think many would find convenient.
We were already using the format you described in your email for the
1.4 ppc discs, with the exception that I created different disc1's
containing a subset of all stages. For the rest they were identical.
There was no grp on disc 1.
Biggest advantage is that you can update grp only, without having to
recreate the disc one.
Also, it removes the requirement to maintain two lists of binary
packages.
The reason for choosing this format for the ppc disc made building a
release much easier:
Unpack a stage3
emerge --buildpkg $PACKAGES
emerge --unmerge $UNWANTED
When finished you have a complete set of GRP, and a kde/gnome cd.
Creating the smaller cds, is just rerunning the script using the GRP
built for kde/gnome but a smaller set of $PACKAGES and a different $USE
of course.
On ppc , pre-releases are for generic ppc only (compatible with
G3,G4,G5). Fosdem release is therefore in the format you described. For
the official release, I want to reduce the set even further by making
only one disc 1 for G3,G4 and G5 (G5 uses a different kernel, but
identical initrd and live environment).
Pieter
>
> Please let me know what you think of this new layout proposal.
>
> Regards,
>
> Daniel
>
>
> --
> gentoo-releng@gentoo.org mailing list
>
--
gentoo-releng@gentoo.org mailing list
next prev parent reply other threads:[~2004-02-18 14:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 7:52 [gentoo-releng] x86 (ppc?) cd layout for 2004.0 Daniel Robbins
2004-02-18 8:36 ` Sven Vermeulen
2004-02-18 14:22 ` Pieter Van den Abeele
2004-02-18 17:18 ` Daniel Robbins
2004-02-18 20:23 ` Sven Vermeulen
2004-02-18 22:45 ` Pieter Van den Abeele
2004-02-18 9:00 ` Seemant Kulleen
2004-02-18 10:35 ` Ciaran McCreesh
2004-02-18 17:20 ` Daniel Robbins
2004-02-18 14:08 ` Pieter Van den Abeele [this message]
2004-02-18 15:31 ` [gentoo-releng] x86 (ppc?) cd layout for 2004.0[Message Scanned] John Davis
2004-02-19 13:53 ` [gentoo-releng] x86 (ppc?) cd layout for 2004.0 Sven Vermeulen
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=EC9EFD8F-621B-11D8-8B24-0003938E7E46@gentoo.org \
--to=pvdabeel@gentoo.org \
--cc=gentoo-releng@lists.gentoo.org \
--cc=klieber@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