From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Stupid USE defaults that need cleaning
Date: Mon, 26 Dec 2005 12:15:42 -0700 [thread overview]
Message-ID: <pan.2005.12.26.19.15.42.5269@cox.net> (raw)
In-Reply-To: 55309248.20051226185355@gentoo.org
Jakub Moc posted <55309248.20051226185355@gentoo.org>, excerpted below,
on Mon, 26 Dec 2005 18:53:55 +0100:
>
> 26.12.2005, 18:07:45, Ciaran McCreesh wrote:
>
>> On Mon, 26 Dec 2005 17:57:17 +0100 Jakub Moc <jakub@gentoo.org> wrote:
>> | alsa - this does not make most sense definitely, this horrible thing
>> | needs to die.
>
>> Why? On x86, alsa is the least broken sound system, and on x86, the
>> target for the default profiles is desktops, and most desktops have
>> soundcards.
>
> Uh eh... I meant *arts*, no clue how I wrote alsa.
USE=arts is a great default, again, by the definition already given "for
packages that can optionally support arts, should it be enabled by default
or not". Most of the arts-optional packages will be KDE. KDE by default
should be arts-aware, at least in KDE 3.x. 4.x will be a different
matter, but with 3.x, while KDE /can/ run without arts, it's /designed/ to
run /with/ arts, so that's the entirely logical default.
Of course, there are packages such as xmms that don't have an direct
relationship to KDE save that they optionally support arts. Great! For
such packages there's this user-configurable file in /etc/portage called
package.use. For those that don't want arts at all, simply set -arts in
make.conf and be done with it. Meanwhile, USE=arts remains an entirely
logical default.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-12-26 19:20 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 ` Duncan [this message]
2005-12-26 19:03 ` 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
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=pan.2005.12.26.19.15.42.5269@cox.net \
--to=1i5t5.duncan@cox.net \
--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