public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Revisions for USE flag changes
Date: Sun, 13 Aug 2017 02:52:58 +0000 (UTC)	[thread overview]
Message-ID: <pan$e1789$17d712eb$ce61a4b2$e27a6476@cox.net> (raw)
In-Reply-To: f3e16f8e-f846-22ec-2342-75801db61ed6@gentoo.org

Michael Orlitzky posted on Sat, 12 Aug 2017 05:58:41 -0400 as excerpted:

> On 08/12/2017 04:39 AM, Paweł Hajdan, Jr. wrote:
> 
>> There are use-cases for --changed-use / --newuse other than changed
>> IUSE.
>> 
>> I find it useful to easily rebuild affected packages when changing USE
>> flags in make.conf. If the flags were removed, would we have a good
>> alternative?
>> 
> I simply overlooked the global USE change in make.conf because IMO it's
> a nonsense operation

??

How so?  Are you arguing that deciding to system-wide switch to/from 
pulseaudio, systemd, or gstreamer is nonsense?

If so, I suspect many gentooers including myself strongly disagree.  If 
not, I'd be interested in what you propose as an alternative to changing 
the appropriate USE flag systemwide, for what is after all a systemwide 
change.

Just seems to me an extremely surprising and unexpected argument, so I'd 
like to understand more of the reasoning behind it.  I'll very likely 
learn something, as invariably the answer to questions I find myself 
compelled to ask due to what appears to me a transparently obvious 
different answer, reveal an angle I hadn't previously considered, 
sometimes changing my mind entirely. =:^)

-- 
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



  reply	other threads:[~2017-08-13  2:53 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-11 23:50 [gentoo-dev] Revisions for USE flag changes Michael Orlitzky
2017-08-12  0:45 ` Brian Evans
2017-08-12  0:59   ` Michael Orlitzky
2017-08-12  1:04     ` Michael Orlitzky
2017-08-12  1:11     ` Brian Evans
2017-08-12  8:39       ` Paweł Hajdan, Jr.
2017-08-12  9:58         ` Michael Orlitzky
2017-08-13  2:52           ` Duncan [this message]
2017-08-13 10:11             ` [gentoo-dev] " Michael Orlitzky
2017-08-13 10:18               ` M. J. Everitt
2017-08-14  1:34                 ` Duncan
2017-08-16 20:12               ` Daniel Campbell
2017-08-18 14:50             ` Duncan
2017-08-13  5:01           ` [gentoo-dev] " Hans de Graaff
2017-08-13 10:38             ` Michael Orlitzky
     [not found]               ` <CAJ0EP42EaW8=dm0c26Gaij9gEAmTVHxiyp5+Hc_CYGzEypudsA@mail.gmail.com>
     [not found]                 ` <CAJ0EP40yVVpLqHL5qVixxgvMmJc7ezRsn42qLoe621wS0KF-VA@mail.gmail.com>
     [not found]                   ` <CAJ0EP43YbX-vA5cWcFm_Etin4H31Nq2s_xYsrTwuOK6LVyW+9A@mail.gmail.com>
     [not found]                     ` <CAJ0EP42HkoYEkL1vt=Lyt-Dw-1XkdAXed8DrBp4oYB9j01+PKQ@mail.gmail.com>
2017-08-13 17:28                       ` Mike Gilbert
2017-08-12  4:22 ` [gentoo-dev] " Michael Palimaka
2017-08-12 10:16   ` Michael Orlitzky
2017-08-12 10:58     ` Michael Palimaka
2017-08-12 10:32   ` Rich Freeman
2017-08-12  5:02 ` [gentoo-dev] " Hans de Graaff
2017-08-12  7:03 ` Michał Górny
2017-08-12  9:57   ` Michael Orlitzky
2017-08-12 10:04     ` Toralf Förster
2017-08-12 10:29     ` Rich Freeman
2017-08-12 11:05       ` [gentoo-dev] " Michael Palimaka
2017-08-12 11:18         ` Rich Freeman
2017-08-14 12:01         ` Jason Zaman
2017-08-16  3:22           ` Michael Orlitzky
2017-08-16 15:56             ` Duncan
2017-08-16 16:09               ` Rich Freeman
2017-08-17  4:27             ` Jason Zaman
2017-08-12 14:14       ` [gentoo-dev] " Michael Orlitzky
2017-08-13  2:32         ` [gentoo-dev] " Duncan
2017-08-13 10:08           ` Michael Orlitzky
2017-08-13 16:06 ` [gentoo-dev] " William Hubbs
2017-08-13 16:12   ` Michael Orlitzky
2017-08-14 16:29     ` William L. Thomson Jr.
2017-08-14 16:21 ` William L. Thomson 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='pan$e1789$17d712eb$ce61a4b2$e27a6476@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