From: Andrew Muraco <tuxp3@leetworks.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Stupid USE defaults that need cleaning
Date: Mon, 26 Dec 2005 17:31:34 -0500 [thread overview]
Message-ID: <43B06F46.3040504@leetworks.com> (raw)
In-Reply-To: <1135635587.7410.32.camel@localhost>
Lares Moreau wrote:
>On Mon, 2005-12-26 at 12:36 -0600, Joe McCann wrote:
>
>
>>For the record, the eds flag was
>>added as a default flag because every 3rd gnome user would file bugs or
>>complain via forums because they installed gnome, found no
>>evolution-data-server integration, and then be bummed when they had to
>>recompile packages again. This whole thread seems to have come from a
>>misunderstanding of how use.defaults work and 20 min of boredom.
>>
>>
>I'm relatively ignorant of USE Flag intricacies, so please forgive me if
>things don't 'fit'.
>
>Is it feasible and or useful to have a 'meta-flag' that that enables all
>the 'necessary' USE flags for a given group of packages? So something
>like USE='meta-<flagname>'.
>This has the distinction of being a meta-flag, and as such nothing
>really gets turned on 'behind the users back', advanced users can look
>into it and see what is being enabled by it and USE='-flag' for the
>flags the users doesn't need/want, and expert users would just not use
>it. This way meta packages like KDE and Gnome can have their own
>meta-flag to do what the need with.
>
>It also seems to me that more things will need to 'just work' as our
>user-base becomes larger and, on average, less advanced. We could amend
>the desktop guide to include something like USE='meta-gnome' to the
>gnome section. And similar to other meta-flags.
>
>This may add an unnecessary level of complexity to the use flag system,
>but also may be very useful.
>
>
If I remember right theres a GLEP (#29) that purposes to do something
very similar (USE Groups I think it was called), but I believe its
withdrawn.
Regards,
Andrew
Tux
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-12-26 22:34 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-26 5:09 [gentoo-dev] Stupid USE defaults that need cleaning Doug Goldstein
2005-12-26 6:09 ` Mike Frysinger
2005-12-26 6:22 ` Dale
2005-12-26 16:27 ` Jan Kundrát
2005-12-26 7:24 ` Doug Goldstein
2005-12-26 7:33 ` Mike Frysinger
2005-12-26 12:53 ` Bastiaan Visser
2005-12-26 13:12 ` Petteri Räty
2005-12-26 16:32 ` Jan Kundrát
2005-12-26 16:44 ` Diego 'Flameeyes' Pettenò
2005-12-26 18:28 ` Andrew Muraco
2005-12-26 12:45 ` Danny van Dyk
2005-12-26 11:35 ` Luca Barbato
2005-12-26 15:35 ` Ciaran McCreesh
2005-12-26 16:57 ` Re[2]: " Jakub Moc
2005-12-26 17:07 ` Ciaran McCreesh
2005-12-26 17:53 ` Re[2]: " Jakub Moc
2005-12-26 19:15 ` [gentoo-dev] " Duncan
2005-12-26 19:03 ` [gentoo-dev] " Carsten Lohrke
2005-12-26 20:06 ` Ciaran McCreesh
2005-12-26 18:36 ` Re[2]: " Joe McCann
2005-12-26 19:00 ` Carsten Lohrke
2005-12-26 19:24 ` Re[4]: " Jakub Moc
2005-12-26 20:48 ` Joe McCann
2005-12-26 21:02 ` Stephen P. Becker
2005-12-26 21:21 ` Diego 'Flameeyes' Pettenò
2005-12-26 21:47 ` Re[2]: " Jakub Moc
2005-12-26 22:19 ` Lares Moreau
2005-12-26 22:28 ` Ciaran McCreesh
2005-12-26 22:31 ` Andrew Muraco [this message]
2005-12-27 1:29 ` Dale
2005-12-27 4:28 ` Chandler Carruth
2005-12-27 4:43 ` Brian Harring
2005-12-27 5:10 ` Chandler Carruth
2005-12-27 5:30 ` Brian Harring
2005-12-28 17:05 ` Olivier Fisette
2005-12-30 18:07 ` Chris Gianelloni
2005-12-26 17:08 ` Simon Stelling
2005-12-26 18:34 ` Doug Goldstein
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=43B06F46.3040504@leetworks.com \
--to=tuxp3@leetworks.com \
--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