From: Maciej Mrozowski <reavertm@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] introspection use flag
Date: Fri, 6 May 2011 20:04:48 +0200 [thread overview]
Message-ID: <201105062004.48810.reavertm@gmail.com> (raw)
In-Reply-To: <4DC3F51C.5070406@gentoo.org>
[-- Attachment #1: Type: Text/Plain, Size: 2255 bytes --]
On Friday 06 of May 2011 15:18:20 Marijn wrote:
> On 05/06/11 14:25, Gilles Dartiguelongue wrote:
> > Le vendredi 06 mai 2011 à 10:40 +0200, Marijn a écrit :
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >>
> >> Dear all,
> >>
> >> I was just looking into the meaning of the introspection use-flag and
> >> there are many ebuilds that use it so perhaps it should be globalized,
> >> which would also give us a chance to improve the naming/description.
> >> Current descriptions are:
> >>
> >> Use dev-libs/gobject-introspection for introspection
> >> Enable GObject introspection.
> >>
> >> Currently it is hard to tell which functionality is enabled through this
> >> flag and the meaning of the descriptions for when the flag is off are
> >> even more unclear. Does it mean that introspection will not be used or
> >> will some other way of introspection be used? Either way, perhaps the
> >> people in the know could shed some light on this issue?
> >>
> >> Thanks,
> >>
> >> Marijn
> >
> > See original thread on this mailing list:
> >
> > From: Arun Raghavan <ford_prefect@gentoo.org>
> > Subject: [gentoo-dev] New global USE flag: introspection
> > Date: Sun, 20 Jun 2010 20:12:58 +0530 (20/06/2010 16:42:58)
> > Message-ID:
> > <AANLkTimjJIGW6k5vQCX-wryeYy_FPUTQpRN7jmW4xRKN@mail.gmail.com>
>
> Thanks for the pointer![1] Having just read that discussion it seems
> that even back then many developers found that the name "introspection"
> is too broad/imprecise. Several alternatives were proposed, like
> gintrospection, gobject-introspection, gir, api-introspection. I think
> any of these would have been better than the current name.
>
> And what happened to the proposed description:
>
> introspection: Add gobject-introspection support, allowing for the
> dynamic generation of bindings for various languages
No.
http://www.mail-archive.com/gentoo-dev@lists.gentoo.org/msg40069.html
> which at least contains a hint of what the purpose is of this flag? But
> maybe someone can do even better than that now that this technology has
> been in use for a while?
>
> Marijn
>
> [1]:http://marc.info/?l=gentoo-dev&m=127704501818312&w=2
--
regards
MM
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-05-06 18:05 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 [this message]
2011-05-06 23:18 ` Nirbheek Chauhan
2011-05-08 20:48 ` Maciej Mrozowski
2011-05-08 21:01 ` [gentoo-dev] " Duncan
2011-05-08 21:29 ` [gentoo-dev] " 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=201105062004.48810.reavertm@gmail.com \
--to=reavertm@gmail.com \
--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