From: Daniel Ostrow <dostrow@gentoo.org>
To: Lars Weiler <pylon@gentoo.org>
Cc: gentoo-releng@lists.gentoo.org, ppc64@gentoo.org, ppc@gentoo.org
Subject: [gentoo-releng] Re: ppc outlines for the release
Date: Wed, 06 Jul 2005 02:19:55 -0400 [thread overview]
Message-ID: <1120630796.7841.15.camel@amd64.anyarch.net> (raw)
In-Reply-To: <20050705224542.GI31682@celeborn.wh-og.hs-niederrhein.de>
[-- Attachment #1: Type: text/plain, Size: 1901 bytes --]
<snip>
> Although ppc64 is able to use multilib, we would do separate
> releases. Well, we could include two squashfs on the LiveCD
> and boot separate kernels, but that will only stress our
> mirrors as every ppc-user has to download stuff he (mostly)
> does not need.
Agreed. ppc and ppc64 will have separate livecds for this release.
<snip>
> ppc32 is missing a 2005.1-profile! This is urgent and must
> be done soon, so that I can test it. Changes would be to
> create profiles for G3, G4, Pegasos, rs6k and OldWorld.
> Mostly some USE-Flags must be set or another default
> bootloader.
>
> ppc64 has a nice new profile, but it seems that there are
> some hickups ;-)
The new profiles are in and all under
default-linux/ppc/2005.1/{ppc,ppc64}. Check them out while they are
still hot.
> We want to cut the support of too many stages and GRP-sets.
> My aim is:
> * ppc32-generic (ppc60x, G3/ppc75x)
> * ppc32-altivec (G4/ppc74xx)
> * ppc64
Speaking only for ppc64, we have MANY potential targets and have yet to
finalize a decision on what we will be providing stages for, what will
be going on the main mirrors and what will be hitting bit-torrent. The
multilib targets are still a bit too fresh in my opinion to be
considering making something as popular as the G5 stages multilib only,
chances are that there will be both 32 and 64-bit userland releases.
Multilib stuff is probably going to be bit-torrent only, or maybe just a
stage1 that users can build off of. There are a lot of choices out there
and I'm trying to be conscious of our mirror space.
Regarding ppc32 I see the following as a good target:
Generic ppc32 stage1
Generic ppc32 stage2
G4 stage2
Generic ppc32 stage3
G4 stage3
Pegasos stage3
This leaves users the ability to create a G3 optimized system off of the
Generic stage{1,2}.
<snip>
Thanks,
--Dan
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-07-06 6:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-05 22:45 [gentoo-releng] ppc outlines for the release Lars Weiler
2005-07-06 6:19 ` Daniel Ostrow [this message]
2005-07-06 7:17 ` [gentoo-releng] " Lars Weiler
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=1120630796.7841.15.camel@amd64.anyarch.net \
--to=dostrow@gentoo.org \
--cc=gentoo-releng@lists.gentoo.org \
--cc=ppc64@gentoo.org \
--cc=ppc@gentoo.org \
--cc=pylon@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