From: Kumba <kumba@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] laying out arch profiles
Date: Sun, 15 Jul 2007 04:28:34 -0400 [thread overview]
Message-ID: <4699DAB2.5080002@gentoo.org> (raw)
In-Reply-To: <1184006865.8412.20.camel@inertia.twi-31o2.org>
Chris Gianelloni wrote:
> On Thu, 2007-07-05 at 18:47 -0400, Mike Frysinger wrote:
>> you proposing we rearchitect it all or just for testing purposes before going
>> live ? i can see both ...
>
> I am proposing rethinking all of it. My current thoughts run something
> like this:
>
> arch/amd64
> arch/ppc (not ppc/ppc64 or ppc/ppc32)
> base
> default/linux
> default/freebsd
> default/macos
> kernel/darwin
> kernel/linux
> kernel/freebsd
> release/2007.1
> target/desktop
> target/server
> userland (these aren't all the same type of thing)
> userland/32-bit
> userland/64-bit
> userland/multilib
> userland/freebsd
> userland/hardened
> userland/linux (this could be glibc, instead)
> userland/macos
> userland/no-nptl (not sure we really need this, at all)
> userland/nptl (this either)
> userland/selinux
> userland/uclibc
>
> Of course, this is just my rough outline. What you would end up with,
> as a profile, is something like this:
>
> default/linux/amd64/2007.1/desktop (not much different from now)
I kinda thought up a system like this long ago, but it was more in line with
node-based profiles. And wou;d've required gutting the current profile code in
portage entirely. The idea being that, you construct the profile up in nodes
from the top level (much like one does their PATH variable), and the profiles
would be re-arranged into things like arch/, libc/, kernel/, etc.. In a way, I
re-organized mips' 2007.1-dev profiles to quasi reflect how we'd look in such a
layout.
But I like this idea -- it goes halfway towards nodes to some extent (at least
lines things up for nodes or some other implementation that maybe treats parents
better).
antarus even had a small draft document up on it that's better in detail:
http://dev.gentoo.org/~antarus/essays/mixin-profiles.txt
(later on, it was decided that there would have to be a pre-defined order for
the first four nodes: base:arch:kernel:userland, and these first four nodes
could not repeat. Everything thereon after was swappable and allowed to be
placed in any order, such as base:mips:linux:glibc:ip30:o32 (where o32/ip30 can
be swapped around))
But I definitely see this as a 2008.0 thing at the earliest. I also see no
problem with mips joining in on the fun to play with things either!
--Kumba
--
Gentoo/MIPS Team Lead
"Such is oft the course of deeds that move the wheels of the world: small hands
do them because they must, while the eyes of the great are elsewhere." --Elrond
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2007-07-15 8:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 16:31 [gentoo-dev] laying out arch profiles Mike Frysinger
2007-07-05 21:18 ` Chris Gianelloni
2007-07-05 22:47 ` Mike Frysinger
2007-07-06 8:15 ` [gentoo-dev] " Steve Long
2007-07-06 15:16 ` Mike Frysinger
2007-07-09 18:47 ` [gentoo-dev] " Chris Gianelloni
2007-07-09 19:04 ` Fabian Groffen
2007-07-15 8:28 ` Kumba [this message]
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=4699DAB2.5080002@gentoo.org \
--to=kumba@gentoo.org \
--cc=gentoo-dev@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