public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Adding USE=udev to linux profiles
Date: Fri, 20 Jul 2018 09:47:06 -0400	[thread overview]
Message-ID: <c4ce7c56-e63b-b099-351d-f65a76361952@gentoo.org> (raw)
In-Reply-To: <CAGfcS_=dDt0Sp+BKKHwZQKyJFAzMW41RD=d1YJMZLAMGJMuUSw@mail.gmail.com>

On 07/20/2018 07:55 AM, Rich Freeman wrote:
> 
> While I agree that setting USE=-udev isn't the same as leaving it to
> package defaults, you further claim that setting this globally causes
> severe breakage in some cases.  Can you provide an example of this?
> 

https://bugs.gentoo.org/640226

Or see any thread on the dangers of USE="-*" which is dangerous for the
same reason.


  reply	other threads:[~2018-07-20 13:47 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-19 21:51 [gentoo-dev] Adding USE=udev to linux profiles Ben Kohler
2018-07-19 22:00 ` Michael Orlitzky
2018-07-19 22:32   ` Ben Kohler
2018-07-20  3:49   ` Aaron Bauman
2018-07-20  4:04     ` Michael Orlitzky
2018-07-20  5:06       ` Mart Raudsepp
2018-07-20  5:58         ` Michael Orlitzky
2018-07-20  6:12           ` Mart Raudsepp
2018-07-20  6:25             ` Michael Orlitzky
2018-07-21  7:01               ` Dennis Schridde
2018-07-21  9:33                 ` Zac Medico
2018-07-21 13:33                   ` Rich Freeman
2018-07-24 17:15                     ` Ian Stakenvicius
2018-07-24 17:55                       ` Dennis Schridde
2018-07-24 18:32                         ` Ian Stakenvicius
2018-07-24 18:57                           ` Rich Freeman
2018-07-24 21:11                             ` Dennis Schridde
2018-07-24 21:16                               ` Rich Freeman
2018-07-21 14:45                   ` Dennis Schridde
2018-07-22 17:52                 ` Michael Orlitzky
2018-07-24 17:40                   ` Ian Stakenvicius
2018-07-20 11:55           ` Rich Freeman
2018-07-20 13:47             ` Michael Orlitzky [this message]
2018-07-20 13:51               ` Rich Freeman
2018-07-20 13:58         ` Peter Stuge
2018-07-20 12:25       ` Ben Kohler
2018-07-20 12:39       ` nado
2018-07-20 12:53         ` Rich Freeman
2018-07-20 13:05         ` nado
2018-07-20 13:14           ` Rich Freeman
2018-07-20 17:08             ` Roy Bamford
2018-07-20 13:17         ` M. J. Everitt
2018-07-20 13:39           ` Rich Freeman
2018-07-20  7:37   ` Matt Turner
2018-07-20 14:13     ` Michael Orlitzky
2018-07-21 16:59       ` Matt Turner
2018-07-22 15:42         ` Chí-Thanh Christopher Nguyễn
2018-07-22 18:13         ` Michael Orlitzky
2018-07-20  1:42 ` Andrew Savchenko
2018-07-20  1:54   ` Mikle Kolyada
2018-07-20  3:52     ` Aaron Bauman
2018-07-20 12:20     ` Ben Kohler
2018-07-20 13:07       ` M. J. Everitt
2018-07-20  1:58   ` Rich Freeman
2018-07-20  3:53     ` Aaron Bauman
2018-07-20  3:51   ` Aaron Bauman
2018-07-20 11:48     ` Andrew Savchenko
2018-07-20  3:40 ` Benda Xu
2018-07-20  5:09   ` Mart Raudsepp
2018-07-20  8:01     ` Benda Xu
2018-07-20 11:09       ` Mart Raudsepp
2018-07-20 12:22   ` Ben Kohler
2018-07-23  5:47 ` Andreas K. Huettel
2018-07-23 15:03   ` Mike Gilbert
2018-07-24 15:05     ` Andrew Savchenko
2018-07-24 15:39       ` Mike Gilbert
2018-07-24 16:06         ` Michael Orlitzky
2018-07-24 16:14           ` Rich Freeman
2018-07-24 16:27             ` Michael Orlitzky
2018-07-24 16:37               ` Rich Freeman
2018-07-24 16:49                 ` Michael Orlitzky
2018-07-24 17:19                   ` Rich Freeman
2018-07-25  7:28             ` Andrew Savchenko
2018-07-25 13:05               ` Ben Kohler
2018-07-26 23:48                 ` Benda Xu
2018-07-26 23:46             ` Benda Xu
2018-07-24 16:24           ` Mike Gilbert
2018-07-24 16:32             ` Michael Orlitzky
2018-07-24 16:46               ` Mike Gilbert
2018-07-26  7:59 ` Andrew Savchenko
2018-07-26 13:07   ` Ben Kohler

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=c4ce7c56-e63b-b099-351d-f65a76361952@gentoo.org \
    --to=mjo@gentoo.org \
    --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