public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: Arun Raghavan <ford_prefect@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org, gnome <gnome@gentoo.org>
Subject: [gentoo-dev] Re: New global USE flag: introspection
Date: Sun, 20 Jun 2010 21:37:41 +0200	[thread overview]
Message-ID: <1277062661.5210.4.camel@localhost.localdomain> (raw)
In-Reply-To: <AANLkTimjJIGW6k5vQCX-wryeYy_FPUTQpRN7jmW4xRKN@mail.gmail.com>

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

El dom, 20-06-2010 a las 20:12 +0530, Arun Raghavan escribió:
> Hi folks,
> I'd like to propose a new global USE-flag: introspection.
> 
> The purpose of the flag is to enable the building of GIR for the
> package using dev-libs/gobject-introspection. gobject-introspection is
> going to be quite important in upcoming GNOME releases, allowing for
> the automated generation of bindings for several languages.
> 
> We already have 13 packages using this flag, with several more to
> come. The current description being used in packages' metadata.xml
> sucks - I'll put something more descriptive in the final flag.
> 
> Any objections? I'll wait till Wed (June 23rd) before adding this if
> there aren't any.
> 
> Cheers!

I agree with having it as a new global USE-flag, but I am unsure about
enabling it by default just now, since some automagic dependency
problems appeared some time ago :-/, but I will leave this decision to
other Gnome team members as I don't know much about introspection and
maybe these issues got fixed already

Best regards



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-06-20 19:38 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 ` Pacho Ramos [this message]
2010-06-20 21:35   ` [gentoo-dev] " 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."
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=1277062661.5210.4.camel@localhost.localdomain \
    --to=pacho@gentoo.org \
    --cc=ford_prefect@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gnome@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