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: introspection use flag
Date: Sun, 8 May 2011 21:01:01 +0000 (UTC)	[thread overview]
Message-ID: <pan.2011.05.08.21.01.00@cox.net> (raw)
In-Reply-To: 201105082248.40204.reavertm@gmail.com

Maciej Mrozowski posted on Sun, 08 May 2011 22:48:39 +0200 as excerpted:

> Nirbheek... and what's particularly wrong with 'introspection' global
> USE flag having implementation-agnostic "Enable runtime API
> introspection" description?
> 
> Nobody sees anything wrong with overly vague 'xml' global USE flag and
> my proposition isn't worse ('Add support for XML files' ... you mean
> what support? import/export or just expat vs libxml2?)

FWIW, I believe it's more a case of "what's done is done, and it's more 
hassle than anybody's been willing to take to fix it now" in the case of 
USE=xml, than not seeing anything wrong with it.  But just because there's 
already such examples in wide use in the tree doesn't mean we need or want 
more of them!

Certainly that's my feeling as a Gentoo sysadmin trying to make sense of 
such flags and how they affect various packages, especially when a bug 
ends up being USE-flag dependent and I need to know whether I actually 
need that functionality or not.

-- 
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:[~2011-05-08 21:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-06  8:40 [gentoo-dev] introspection use flag Marijn
2011-05-06 12:25 ` Gilles Dartiguelongue
2011-05-06 13:18   ` Marijn
2011-05-06 13:30     ` Gilles Dartiguelongue
2011-05-06 18:04     ` Maciej Mrozowski
2011-05-06 23:18       ` Nirbheek Chauhan
2011-05-08 20:48         ` Maciej Mrozowski
2011-05-08 21:01           ` Duncan [this message]
2011-05-08 21:29           ` Nirbheek Chauhan
2011-05-06 12:55 ` Nirbheek Chauhan

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.2011.05.08.21.01.00@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