From: solar <solar@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Subject: Re: [gentoo-releng] Feature Requests for 2006.1
Date: Tue, 14 Mar 2006 14:27:00 -0500 [thread overview]
Message-ID: <1142364420.27828.51.camel@onyx> (raw)
In-Reply-To: <1142354519.21388.12.camel@cgianelloni.nuvox.net>
You cant really do a server profile so far nested within the
default-linux profiles. The flags will be just wrong.
Also a server is not something you should be switching profiles every 6
months.
If you are serious about a server profile I'd suggest dropping what you
are thinking now. Lets have a meeting (hardened + server + infra +
releng ) folks and do it right together.
On Tue, 2006-03-14 at 11:41 -0500, Chris Gianelloni wrote:
> Alright people, I'm starting up the feature requests for the 2006.1
> release. Some things to remember when making requests:
>
> - We don't control what is stable in the tree, so requests for specific
> packages won't be useful to us. If you want a specific package added to
> the release media, there are two steps required. First, the package
> must be marked stable on any architecture which will be using the
> package. Second, a bug should be filed requesting the package be added.
> Please make sure that your request has not already been filed before
> filing a new bug report.
> - We don't control portage features.
> - We don't control kernel versions, but we do control which *-sources we
> use and also the configurations of those kernels.
>
> A few ideas on things you can request are:
>
> - New modules added to the release media
> - New packages added to GRP/LiveCD/LiveDVD
> - New media types (LiveDVD/netboot/*)
> - Additional USE flags enabled/disabled by default
>
> I am currently working on a new set of profiles for 2006.1 on x86. As
> you can tell, these profiles are a bit different from anything else that
> we have done in the past, as it separates out into "desktop" and
> "server" profiles. The "desktop" profile is very similar to what we
> have always had on each release. The "server" profile is new, and has
> none of the typical desktop USE flags enabled, making it ideal for
> server usage. I plan on also creating some sort of "developer" profile
> which will inherit from both "desktop" and "server" profiles, once
> portage has support for multiple inheritance, so it might not make it
> into the 2006.1 profiles. I am looking for suggestions for USE flags to
> add to these two profiles, so feel free to make suggestions. Please
> cite some reasoning for why you think each USE flag you recommend should
> be either enabled or disabled. The profiles are at
> profiles/default-linux/x86/dev/2006.1/desktop and
> profiles/default-linux/x86/dev/2006.1/server for you to peruse. They
> are completely functional profiles at this time.
>
--
solar <solar@gentoo.org>
Gentoo Linux
--
gentoo-releng@gentoo.org mailing list
next prev parent reply other threads:[~2006-03-14 19:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 16:41 [gentoo-releng] Feature Requests for 2006.1 Chris Gianelloni
2006-03-14 19:00 ` Sven Vermeulen
2006-03-14 19:06 ` Andrew Gaffney
2006-03-14 19:27 ` solar [this message]
2006-03-14 19:51 ` Chris Gianelloni
2006-03-14 20:18 ` solar
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=1142364420.27828.51.camel@onyx \
--to=solar@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