From: Mike Auty <ikelos@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: New global USE flag: introspection
Date: Tue, 22 Jun 2010 21:17:04 +0100 [thread overview]
Message-ID: <4C211A40.6070001@gentoo.org> (raw)
In-Reply-To: <AANLkTinxwN6TiwTry5eTjVZE2Bbe1yZb3dkn9rZ8O8kW@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 22/06/10 18:11, Arun Raghavan wrote:
> It is not a GNOME-only flag.
A general introspection flag may not be, but this isn't a general
introspection flag, this is specific to gobject and the suggestions try
to clarify that. People who want gobject-introspection (which concerns
gobject, and is therefore appropriate for a "g" prefix) will not want to
have to manually differentiate between arbitrary-library-introspection
and gobject-introspection by fiddling around with a package.use file to
individually turn it on and off. It should be an easy, global USE flag
to enable once in make.conf and forget about.
> Which should not be an issue since any library that has some sort of
> introspection can use this flag (and the use.desc can be changed
> appropriately at that time if it does not use gobject-introspection).
Why have to change it in the future (and probably split it into two
flags then), when the choice hasn't been made yet? Or, to put your own
question to you, why are you vehemently for "introspection" when others
have shown concern with the choice? As far as I can see, the only
difference is requiring a slightly longer use_enable line.
In the end, it's not a big issue and whichever is chosen it'll work out.
I'm just trying to figure out why the compromise solutions aren't good
enough to satisfy everyone?
Mike 5:)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
iEYEARECAAYFAkwhGkAACgkQu7rWomwgFXp0dQCePjaHQn6JeBO6OrzwsIHBp8f1
+2gAoJDD4MS1spuo1DiqD96uOfX8ZBj9
=TJvC
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-06-22 20:17 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."
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 [this message]
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=4C211A40.6070001@gentoo.org \
--to=ikelos@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