From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Subject: [gentoo-releng] Profile Reorganization
Date: Wed, 02 Nov 2005 09:33:31 -0500 [thread overview]
Message-ID: <1130942011.26789.225.camel@cgianelloni.nuvox.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1403 bytes --]
Alright, I've had this idea for ways to reorganize the profiles for some
time now. I figured now would be as good a time as any to introduce it
here, since we probably do more profile work than anyone else. Once
we've got a decent idea hashed out, we can GLEP it and make the changes
in the tree.
Basically, it is a reorganization of the profiles to make more sense.
Profiles would consist of:
$type/$kernel/$userland/$arch/($version)
Now, type would be the main type of profile. To match with what we have
now, we would have "default" which is the default release profile,
"hardened" and "uclibc". We would keep the "base" profile, where the
globally-affecting things would remain. The kernel would be the kernel
in use. I believe that currently, we would have "linux", "darwin", and
"freebsd". The userland would be "gnu" or "bsd". Of course, arch is
pretty obvious. Everything below arch would be optional profiles. For
Release Engineering, this would be where we would put our versioned
release profiles, along with any other sub-profiles.
All that this really accomplishes it a bit of cleanup of the profiles,
but also allows for greater support of more interesting profiles, such
as a hardened Linux profile with a BSD userland on Alpha.
--
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-11-02 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 14:33 Chris Gianelloni [this message]
2005-11-05 2:11 ` [gentoo-releng] Profile Reorganization Kumba
2005-11-05 3:19 ` Ciaran McCreesh
2005-11-08 22:53 ` Danny van Dyk
2005-11-11 23:37 ` Chris Gianelloni
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=1130942011.26789.225.camel@cgianelloni.nuvox.net \
--to=wolf31o2@gentoo.org \
--cc=gentoo-releng@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