public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: New global USE flag: introspection
Date: Mon, 21 Jun 2010 09:04:03 +0200	[thread overview]
Message-ID: <4C1F0EE3.5010208@gentoo.org> (raw)
In-Reply-To: <AANLkTilY9ceZ4RAoiKFz28w_kOwVcQgCK7pFdeJ6lGX-@mail.gmail.com>

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

On 6/21/10 8:53 AM, Arun Raghavan wrote:
> On 21 June 2010 11:43, Alexis Ballier <aballier@gentoo.org> wrote: 
> [...]
>>> introspection: Add gobject-introspection support, allowing for
>>> the dynamic generation of bindings for various languages
>> 
>> why not naming the useflag gobject-introspection then ?
> 
> Mostly because it seems exceedingly verbose to me (yes, I know we
> have longer USE flags, and I find them too long as well).

Please take a look at the devmanual,
http://devmanual.gentoo.org/general-concepts/use-flags/

> In particular, note that if client and server USE flags are ever
> introduced, they can not be global USE flags for this reason.

I think that "introspection" is similarly too general.

So can we either rename it to "gobject-introspection", or find some
other way to handle it?

On the other hand, we already have "handbook" flag for KDE4. So the
above is not really a strong opinion, just a point to consider.

Paweł


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2010-06-21  7:04 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-20 14:42 [gentoo-dev] New global USE flag: introspection Arun Raghavan
2010-06-20 19:37 ` [gentoo-dev] " Pacho Ramos
2010-06-20 21:35   ` Nirbheek Chauhan
2010-06-20 21:53     ` Pacho Ramos
2010-06-20 20:14 ` [gentoo-dev] " Olivier Crête
2010-06-20 21:33   ` Nirbheek Chauhan
2010-06-20 22:55   ` Brian Harring
2010-06-20 23:33     ` Nirbheek Chauhan
2010-06-21  4:43   ` Arun Raghavan
2010-06-21  7:10     ` Michał Górny
2010-06-21  4:44 ` [gentoo-dev] " Arun Raghavan
2010-06-21  6:13   ` Alexis Ballier
2010-06-21  6:53     ` Arun Raghavan
2010-06-21  7:03       ` Alexis Ballier
2010-06-21  7:04       ` "Paweł Hajdan, Jr." [this message]
2010-06-21  9:07         ` Duncan
2010-06-21 13:46           ` Olivier Crête
2010-06-21 14:49             ` Duncan
2010-06-21 13:55         ` René 'Necoro' Neumann
2010-06-21  7:33 ` [gentoo-dev] " Maciej Mrozowski
2010-06-21 14:22   ` Olivier Crête
2010-06-21 15:44     ` Maciej Mrozowski
2010-06-21 15:53       ` Arun Raghavan
2010-06-22  9:47         ` Arun Raghavan
2010-06-22 11:24           ` [gentoo-dev] " Peter Hjalmarsson
2010-06-22 14:33             ` Arun Raghavan
2010-06-22 16:33               ` Mike Auty
2010-06-22 17:11                 ` Arun Raghavan
2010-06-22 20:17                   ` Mike Auty
2010-06-23  4:03                     ` Arun Raghavan
2010-06-25 14:56                       ` Mart Raudsepp
2010-06-22 18:00                 ` Jacob Godserv
2010-06-21 14:49   ` [gentoo-dev] " Nirbheek Chauhan
2010-06-22 17:14 ` [gentoo-dev] " Arun Raghavan
2010-07-23 13:14   ` Maciej Mrozowski

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=4C1F0EE3.5010208@gentoo.org \
    --to=phajdan.jr@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