From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] default desktop profile
Date: Fri, 03 Aug 2007 11:50:17 -0700 [thread overview]
Message-ID: <1186167017.8470.8.camel@inertia.twi-31o2.org> (raw)
In-Reply-To: <46B2D4C2.2080507@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1616 bytes --]
On Fri, 2007-08-03 at 09:09 +0200, Rémi Cardona wrote:
> Chris Gianelloni wrote:
> > On Thu, 2007-08-02 at 11:27 +0200, Martin Schwier wrote:
> >> +startup-notification
>
> Actually, rereading that list, I wouldn't mind adding this one. Gnome
> and a couple of core Gnome apps hard-depend on it, as I am must sure
> must be the case in KDE.
>
> Samuli also told me that xcfe4 really needed it anyway. I guess this is
> one where most people would easily agree on adding it to the desktop
> profile.
I've added ppds and startup-notification to the default USE for the
newly-created x86 development profiles for 2007.1, which I'd ask people
to base any change requests on, rather than the 2007.0 profiles.
Basically, if it isn't in the 2007.1 profile and you want it, ask for it
on gentoo-releng. If we think we need more discussion on a particular
USE flag, we'll bring it back here.
One thing to remember, I do *not* consider our desktop profiles to be
"opt-in" but rather to be a good out-of-box experience for the user. If
you want to think of the desktop profiles as bloated, feel free to use
the versioned profile (like 2007.0) instead, as it will be much closer
to the opt-in idea and only has USE flags which are common between
desktops and servers and are much less likely to get additional flags
added to them, since I want these to be as minimal as possible while
still providing important functionality.
--
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Council Member/Foundation Trustee
Gentoo Foundation
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-08-03 18:54 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 9:27 [gentoo-dev] default desktop profile Martin Schwier
2007-08-02 11:38 ` [gentoo-dev] " Steve Long
2007-08-02 14:22 ` [gentoo-dev] " Rémi Cardona
2007-08-02 15:09 ` [gentoo-dev] " Martin Schwier
2007-08-02 18:47 ` Steev Klimaszewski
2007-08-02 21:40 ` Jean-Marc Hengen
2007-08-02 14:30 ` [gentoo-dev] " Kent Fredric
2007-08-02 15:51 ` Mike Frysinger
2007-08-03 1:35 ` Chris Gianelloni
2007-08-03 1:53 ` Donnie Berkholz
2007-08-03 18:35 ` Chris Gianelloni
2007-08-03 19:56 ` Andrew Gaffney
2007-08-03 21:28 ` Chris Gianelloni
2007-08-03 22:39 ` Roy Marples
2007-08-03 23:18 ` Chris Gianelloni
2007-08-03 23:42 ` Roy Marples
2007-08-04 4:31 ` Luis Medinas
2007-08-04 21:20 ` Andrew Gaffney
2007-08-06 19:20 ` Chris Gianelloni
2007-08-04 6:08 ` Samuli Suominen
2007-08-04 17:09 ` Gilles Dartiguelongue
2007-08-04 21:23 ` Andrew Gaffney
2007-08-04 23:15 ` Gilles Dartiguelongue
2007-08-04 23:20 ` Andrew Gaffney
2007-08-04 21:22 ` Andrew Gaffney
2007-08-06 19:21 ` Chris Gianelloni
2007-08-03 7:09 ` Rémi Cardona
2007-08-03 18:50 ` Chris Gianelloni [this message]
2007-08-03 19:00 ` Petteri Räty
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=1186167017.8470.8.camel@inertia.twi-31o2.org \
--to=wolf31o2@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