From: Chris Stankevitz <chrisstankevitz@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Adding a use flag: hwdb
Date: Mon, 11 Jun 2012 21:29:48 -0700 [thread overview]
Message-ID: <CAPi0psv=wwXi591mUTio6iOGDt=1a-1_Kh9EJN5qTsOwHG1r5g@mail.gmail.com> (raw)
In-Reply-To: <4FD6A7EE.5060700@orlitzky.com>
Michael,
On Mon, Jun 11, 2012 at 7:22 PM, Michael Orlitzky <michael@orlitzky.com> wrote:
> Portage doesn't know what you want to do, so it does the safe thing and
> lets you decide. Either,
Somewhat tongue-in-cheek:
I don't know either. I don't want udev, udisks, hwdb or even know
what they are. Somebody else wants all that stuff on my system
(gentoo profile or the gentoo handbook author) and I wish that person
would have addressed emerge's concerns WRT use flags.
> The ruby_targets_ruby19 thing is a good example of where you may not
> want that behavior by default. Something was screwed up, people noticed
> it, and the devs ultimately fixed it. The most-correct thing to do was
> nothing (i.e. wait).
I didn't know what RUBY was or why it was on my system or who wanted
it or whether that person wanted ruby_targets_ruby19 or RUBY_TARGETS
or whatever. Me "waiting" would require 1) that I knew RUBY was a
"temporary problem" that would be fixed in the future [I assumed it
was not... just like hwdb] and 2) that I not perform an emerge
sync/world.
Thank you!
Chris
next prev parent reply other threads:[~2012-06-12 4:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 2:57 [gentoo-user] Adding a use flag: hwdb Chris Stankevitz
2012-06-11 7:49 ` Alan McKinnon
2012-06-11 8:26 ` Alex Schuster
2012-06-11 23:30 ` Chris Stankevitz
2012-06-12 2:22 ` Michael Orlitzky
2012-06-12 4:29 ` Chris Stankevitz [this message]
2012-06-12 6:26 ` Michael Orlitzky
2012-06-12 7:48 ` Neil Bothwick
2012-06-12 9:45 ` [gentoo-user] " Chris Stankevitz
2012-06-12 16:16 ` Michael Orlitzky
2012-06-11 12:55 ` [gentoo-user] " David W Noon
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='CAPi0psv=wwXi591mUTio6iOGDt=1a-1_Kh9EJN5qTsOwHG1r5g@mail.gmail.com' \
--to=chrisstankevitz@gmail.com \
--cc=gentoo-user@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