From: Luke-Jr <luke-jr@gentoo.org>
To: dams@idm.fr
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] desktop
Date: Fri, 29 Aug 2003 14:18:36 +0000 [thread overview]
Message-ID: <200308291418.48569.luke-jr@gentoo.org> (raw)
In-Reply-To: <m2smnk4kyx.fsf@krotkine.idm.fr>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ok that somewhat explains what 'desktop' is... But what has the *discussion*
been discussing? :)
On Friday 29 August 2003 02:06 pm, dams@idm.fr wrote:
> Luke-Jr <luke-jr@gentoo.org> said:
> > Could someone summarize this thread please? I'm somewhat interested in
> > the discussion, but don't really have time to go through reading all 50
> > or so new messages... o.o;;
>
> summary attempt (please correct me if we still don't agree)
>
> desktop will handle the desktop component. It'll try to stick with vanilla
> desktops as much as possible, but provide good default, and uniformization
> when it's possible and non-intrusive. In all case, additions should be
> easily (un)pluggable.
>
> About non visible stuff, desktop will try to make things work out of the
> box. Ie, addapt config/default data so that they better interact with
> gentoo core system.
>
> Some questions to answer :
>
> - do we want X in desktop or in base or elsewhere? it seems we tend to put
> X in base, but not included in default system
>
> - should we have rules to decide if such modification will change the DE
> too much from vanilla state?
>
> - probably other things, but my head is in a bad state right now
- --
Luke-Jr
Developer, Gentoo Linux
http://www.gentoo.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD4DBQE/T2DFZl/BHdU+lYMRAs++AJiMQdQA2aQxWRqaqeuO22/77AARAJkBj1TW
lVvuVtDKyOpkMMYfonAZIA==
=pCiP
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2003-08-29 14:19 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 22:22 [gentoo-dev] desktop dams
2003-08-27 22:58 ` Spider
2003-08-28 0:41 ` Brett I. Holcomb
2003-08-28 0:47 ` Jon Portnoy
2003-08-28 0:58 ` Cedric Veilleux
2003-08-28 1:29 ` Riyad Kalla
2003-08-28 1:48 ` Stuart Herbert
2003-08-28 8:08 ` dams
2003-08-28 10:25 ` Paul de Vrieze
2003-08-28 10:51 ` dams
2003-08-28 11:08 ` Paul de Vrieze
2003-08-28 11:28 ` dams
2003-08-28 13:37 ` Mike Frysinger
2003-08-29 5:22 ` Luke-Jr
2003-08-28 11:15 ` foser
2003-08-28 12:52 ` dams
2003-08-28 13:21 ` foser
2003-08-28 13:51 ` Stuart Herbert
2003-08-28 14:00 ` Paul de Vrieze
2003-08-28 14:10 ` Michael Cummings
2003-08-28 14:34 ` foser
2003-08-28 14:30 ` foser
2003-08-28 17:44 ` Spider
2003-08-28 19:14 ` Peter Ruskin
2003-08-28 19:24 ` foser
2003-08-28 22:07 ` Peter Ruskin
2003-08-28 20:46 ` dams
2003-08-28 21:34 ` Spider
2003-08-28 22:32 ` foser
2003-08-28 23:01 ` dams
2003-08-28 20:35 ` dams
2003-08-28 21:03 ` Spider
2003-08-28 21:21 ` dams
2003-08-28 22:40 ` foser
2003-08-28 21:07 ` Paul de Vrieze
2003-08-28 14:59 ` dams
2003-08-28 21:17 ` Paul de Vrieze
2003-08-28 23:24 ` Jason Stubbs
2003-08-28 13:54 ` Chris Gianelloni
2003-08-28 15:03 ` dams
2003-08-28 15:09 ` Stuart Herbert
2003-08-28 15:36 ` dams
2003-08-28 15:48 ` jonah benton
2003-08-28 14:04 ` Paul de Vrieze
2003-08-28 14:48 ` foser
2003-08-28 23:30 ` Seemant Kulleen
2003-08-29 1:32 ` Luke-Jr
2003-08-29 14:06 ` dams
2003-08-29 14:18 ` Luke-Jr [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=200308291418.48569.luke-jr@gentoo.org \
--to=luke-jr@gentoo.org \
--cc=dams@idm.fr \
--cc=gentoo-dev@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