From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1I7yKm-0003k4-6U for garchives@archives.gentoo.org; Mon, 09 Jul 2007 18:51:44 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l69IogvJ005148; Mon, 9 Jul 2007 18:50:42 GMT Received: from mail.twi-31o2.org (c-24-6-168-204.hsd1.ca.comcast.net [24.6.168.204]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l69ImlQg002823 for ; Mon, 9 Jul 2007 18:48:48 GMT Received: from localhost (localhost [127.0.0.1]) by mail.twi-31o2.org (Postfix) with ESMTP id 685582480E2 for ; Mon, 9 Jul 2007 14:36:50 -0400 (EDT) X-Virus-Scanned: amavisd-new at twi-31o2.org Received: from mail.twi-31o2.org ([127.0.0.1]) by localhost (gravity.twi-31o2.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GsYILk+tcqtC for ; Mon, 9 Jul 2007 14:36:10 -0400 (EDT) Received: from [192.168.100.53] (dsl211-165-131.sfo1.dsl.speakeasy.net [74.211.165.131]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mail.twi-31o2.org (Postfix) with ESMTP id 4390B248079 for ; Mon, 9 Jul 2007 14:36:10 -0400 (EDT) Subject: Re: [gentoo-dev] laying out arch profiles From: Chris Gianelloni To: gentoo-dev@lists.gentoo.org In-Reply-To: <200707051847.41606.vapier@gentoo.org> References: <200706271231.29549.vapier@gentoo.org> <1183670330.8491.22.camel@inertia.twi-31o2.org> <200707051847.41606.vapier@gentoo.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-x55SC0s8hREnRuXmONw8" Date: Mon, 09 Jul 2007 11:47:45 -0700 Message-Id: <1184006865.8412.20.camel@inertia.twi-31o2.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 X-Archives-Salt: 343fb34d-234f-43a1-a20b-568715176b33 X-Archives-Hash: 43e692e8114ebae78c24b94ea1c28ad7 --=-x55SC0s8hREnRuXmONw8 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2007-07-05 at 18:47 -0400, Mike Frysinger wrote: > you proposing we rearchitect it all or just for testing purposes before g= oing=20 > 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) default inherits from base, then determines the parent path we take, such as glibc over uclibc linux is simple in this case since we're "default" meaning we'll have a Linux kernel and glibc userland amd64 is the architecture, of course... being "default" means it'll be multilib automatically... this level should be the "highest" usable level with the least amount of USE/etc enabled, as it should be only what is required globally plus arch-specific 2007.1 is the release-specific profile and adds in the changes/enhancements from that particular release desktop is the target the profile is designed for, so it would have additional USE enabled I would also love to use package sets in some way in the profiles for defining sets of packages that might be useful to the user without forcing them into the "system" set for that profile. Some examples of what I mean would be adding things like dhcpcd and gentoolkit to the default "desktop" profile without them being in system, so they can be easily removed by users that don't want them. This would, of course, depend on the implementation used for package sets. Taking the above example, to build a hardened server, you'd have something like: hardened/linux/amd64/2007.1/server (again not much different) Of course, this is all just how I've been envisioning doing everything and I'm sure other people have lots of ideas on their own. I'm creating an overlay for these profiles while I work on them, so we can easily get input on them and track the changes. I'd like to get input on this schema for the profiles before I commit anything and am definitely interested in getting input from anyone with any profile experience. Using an overlay will allow us to make changes (to base, for example) without disrupting the tree until we're ready. --=20 Chris Gianelloni Release Engineering Strategic Lead Alpha/AMD64/x86 Architecture Teams Games Developer/Council Member/Foundation Trustee Gentoo Foundation --=-x55SC0s8hREnRuXmONw8 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (GNU/Linux) iD8DBQBGkoLRkT4lNIS36YERAm0vAJ409RlbVms4SYCtw5OCGKtZMTB+sgCeO4Sd 2LWMwgAwpby6O3uIrazuAKE= =KITA -----END PGP SIGNATURE----- --=-x55SC0s8hREnRuXmONw8-- -- gentoo-dev@gentoo.org mailing list