public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] USE_EXPAND is not an IUSE replacement [was: New USE_EXPAND: CLAWS_MAIL_PLUGINS]
Date: Sat, 4 May 2013 12:08:36 -0500	[thread overview]
Message-ID: <20130504170836.GA2331@linux1> (raw)
In-Reply-To: <51847A8D.6000704@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1576 bytes --]

On Fri, May 03, 2013 at 11:03:41PM -0400, Rick "Zero_Chaos" Farina wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 05/03/2013 05:28 PM, Mike Gilbert wrote:
> > On Fri, May 3, 2013 at 5:08 PM, René Neumann <lists@necoro.eu> wrote:
> >> Am 03.05.2013 22:20, schrieb Zac Medico:
> >>> Is it worth changing?
> >>
> >> Nope. What's worth changing is the excessive use of USE_EXPAND for no
> >> reason (your described usecase makes sense for reasonable USE_EXPAND
> >> stuff like VIDEO_CARDS). But seems like I'm the only one concerned by
> >> this, so I should probably rest my case and switch to silent sobbing
> >> instead ;-).
> >>
> >> - René
> >>
> > 
> > Well, I do agree that they are overused. For example, GRUB_PLATFORMS
> > is used by only one package.
> > 
> > I would convert it back into a normal set of use flags, but that would
> > mean any users of sys-boot/grub:2 would have to update their
> > configuration. I don't think it is worth it at this point.
> > 
> 
> Considering grub:2 isn't really used by the majority of users I feel
> compelled to note that you could convert now and just pick a sane set of
> use defaults.  I know it's been a while since EAPI2 was introduced but I
> do love that little feature...  :-)

I would also like to chime in here and point out that all grub:2 users
are ~arch users. If we were going to break stable it would be more of a
shake-up, but since it isn't happening that way, I would say go for it.
~arch users are expected to be able to handle things like this.

William

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-05-04 17:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-21 21:38 [gentoo-dev] New USE_EXPAND: CLAWS_MAIL_PLUGINS Christian Faulhammer
2013-04-24  8:18 ` Gilles Dartiguelongue
2013-04-24  9:51 ` René Neumann
2013-04-24 17:15   ` Zac Medico
2013-04-24 19:48     ` René Neumann
2013-05-30 21:28       ` Zac Medico
2013-05-03 12:59   ` [gentoo-dev] USE_EXPAND is not an IUSE replacement [was: New USE_EXPAND: CLAWS_MAIL_PLUGINS] René Neumann
2013-05-03 20:20     ` Zac Medico
2013-05-03 20:25       ` Ciaran McCreesh
2013-05-03 21:08       ` René Neumann
2013-05-03 21:28         ` Mike Gilbert
2013-05-04  3:03           ` Rick "Zero_Chaos" Farina
2013-05-04 17:08             ` William Hubbs [this message]
2013-05-04  6:11         ` Dustin C. Hatch
2013-05-04 14:27           ` vivo75
2013-05-04 15:02           ` Zac Medico
2013-05-04  2:58       ` Rick "Zero_Chaos" Farina
2013-05-04 15:31         ` Ciaran McCreesh
2013-05-04 16:37           ` Rick "Zero_Chaos" Farina
2013-04-24 18:57 ` [gentoo-dev] New USE_EXPAND: CLAWS_MAIL_PLUGINS Michał Górny
2013-04-28 19:26 ` [gentoo-dev] " Christian Faulhammer

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=20130504170836.GA2331@linux1 \
    --to=williamh@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