From: Luke-Jr <luke-jr@gentoo.org>
To: vapier@gentoo.org, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] desktop
Date: Fri, 29 Aug 2003 05:22:01 +0000 [thread overview]
Message-ID: <200308290522.16819.luke-jr@gentoo.org> (raw)
In-Reply-To: <200308280937.08589.vapier@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
IMO, the USE flag should be needed to enable customizations, not to disable
them. 'vanilla' should be the default with '-*'
On Thursday 28 August 2003 01:37 pm, Mike Frysinger wrote:
> On Thursday 28 August 2003 07:28, dams@idm.fr wrote:
> > Paul de Vrieze <pauldv@gentoo.org> said:
> > > On Thursday 28 August 2003 12:51, dams@idm.fr wrote:
> > >> The problem is that the conclusion will tend to tune/modify the DE,
> > >> and it seems that people here don't want that, they want vanilla DE.
> > >> For ex., menu system is the first improvment I think of, but it has a
> > >> big impact on the look&feel of the DE. If we don't want DE tuned, then
> > >> we cannot use debian like menu system.
> > >
> > > That is true, there might be some custom parts in the DE's. I those
> > > cases I think we should have some "vanilla" useflag that turns of
> > > customizations/hacks that are gentoo-specific and are safe to turn of
> >
> > That's feasable, but may add some maintainance overloading
>
> not really ... any code you add just put 'if [ ! `use vanilla` ] ; then'
> around ...
> http://bugs.gentoo.org/show_bug.cgi?id=8732
> -mike
- --
Luke-Jr
Developer, Gentoo Linux
http://www.gentoo.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/TuMFZl/BHdU+lYMRAiyRAJ0QYtpj1zFrdren4NP4diXUWiFuZwCggrdL
g2mXGpb8DTNZ5t5LHmcNWSQ=
=u29b
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-08-29 5:22 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 [this message]
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
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=200308290522.16819.luke-jr@gentoo.org \
--to=luke-jr@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=vapier@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