Re: [gentoo-dev] Re: New global USE flag: introspection
On 21 June 2010 11:43, Alexis Ballier 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). -- Arun Raghavan http://arunraghavan.net/ (Ford_Prefect | Gentoo) & (arunsr | GNOME)
Re: [gentoo-dev] Re: New global USE flag: introspection
On Monday 21 June 2010 07:44:50 Arun Raghavan wrote: > On 20 June 2010 20:12, Arun Raghavan wrote: > [...] > > > 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. > > Here's the description I'm planning to add: > > introspection: Add gobject-introspection support, allowing for the > dynamic generation of bindings for various languages why not naming the useflag gobject-introspection then ? A. signature.asc Description: This is a digitally signed message part.
[gentoo-dev] Re: New global USE flag: introspection
On 20 June 2010 20:12, Arun Raghavan wrote: [...] > 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. Here's the description I'm planning to add: introspection: Add gobject-introspection support, allowing for the dynamic generation of bindings for various languages Cheers, -- Arun Raghavan http://arunraghavan.net/ (Ford_Prefect | Gentoo) & (arunsr | GNOME)
Re: [gentoo-dev] New global USE flag: introspection
2010/6/21 Olivier Crête : > On Sun, 2010-06-20 at 20:12 +0530, Arun Raghavan wrote: >> I'd like to propose a new global USE-flag: introspection. > ... >> Any objections? I'll wait till Wed (June 23rd) before adding this if >> there aren't any. > > Do we really want it to be a USE flag ? I would force it on always for > everyone. Due to the direction in which GNOME is heading, it will be > required by the core desktop anyway. In addition to what Nirbheek pointed out, I think a USE flag would be useful for embedded setups where you might only want introspection for a subset of libraries. I do agree with you about it being part of the core desktop and required by most users, so it will be enabled by default for all ebuilds. Cheers, -- Arun Raghavan http://arunraghavan.net/ (Ford_Prefect | Gentoo) & (arunsr | GNOME)
Re: [gentoo-dev] Tone in Gentoo
If this thread started out at some point as being constructive, it's certainly stopped being so now. Please kill this, take some cool-off time, and come back if there is something *constructive* to be said. -- Arun Raghavan http://arunraghavan.net/ (Ford_Prefect | Gentoo) & (arunsr | GNOME)
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-python/traits: traits-3.4.0.ebuild
On Sun, Jun 20, 2010 at 06:27:00PM -0400, Mike Frysinger wrote: > On Sunday, June 20, 2010 09:55:39 Arfrever Frehtes Taifersar Arahesis wrote: > > 2010-06-19 22:53:37 Mike Frysinger napisał(a): > > > On Thursday, June 10, 2010 16:45:29 Arfrever Frehtes Taifersar wrote: > > > > 2010-06-10 22:20:44 Nirbheek Chauhan napisał(a): > > > > > On Fri, Jun 11, 2010 at 1:30 AM, Arfrever Frehtes Taifersar wrote: > > > > > > 2010-06-10 21:27:40 Jeremy Olexa napisał(a): > > > > > >> I see no reason to *not* add a ChangeLog entry here. > > > > > > > > > > > > ChangeLog entries are not required for trivial changes. > > > > > > > > > > A "trivial" change is fixing a typo, or a manifest problem, a missing > > > > > quotation mark, etc. Anything else is not "trivial". > > > > > > > > > > Anything that changes how an ebuild functions, what it does, or the > > > > > installed files (and/or their contents) is NOT a trivial change. > > > > > > > > This commit only removed some compiler warnings. > > > > > > mucking with CFLAGS without documentation is wrong. compiler warnings > > > come and go, so a flag that was relevant one day could be completely > > > extraneous the next. > > > > > > however, especially with strict aliasing, you arent "just fixing > > > warnings", you're changing optimization behavior of gcc to workaround > > > broken C code. this obviously does not fall anywhere near the "trivial" > > > mark. > > > > > > i see you still havent fixed this, so get on it already. a bug needs to > > > be opened somewhere to get the package properly *fixed* > > > > This problem is probably caused by bugs in Python 2, which have been fixed > > in Python 3. > > the new information you've provided here only reinforces the fact the current > code is wrong. properly document the append-flags and properly restrict it > to > when python-2 is being used. > > considering python-2 is going to be in our lives for a while, how hard is it > to backport the changes in question to the headers ? presumably it's > struct/union/cast shuffling in the headers. This is upstream python bug 969718 offhand; basically if cflags exists for distutils consumers, base cflags don't make it fully through- meaning no -fno-strict-aliasing as is generally needed for building python extensions. As for py3k, looks of it py3.1 still suffers it. Either way, this is the wrong thing to fix- python's distutils needs fixing, not consumers. In snakeoil, we detect and fix it on the fly to provide a fixed version of distutils, but obviously not many pkgs consume that... ~harring pgppdSJIknTLf.pgp Description: PGP signature
[gentoo-dev] Automated Package Removal and Addition Tracker, for the week ending 2010-06-20 23h59 UTC
The attached list notes all of the packages that were added or removed from the tree, for the week ending 2010-06-20 23h59 UTC. Removals: dev-util/hgsvn 2010-06-15 08:14:01 jlec x11-libs/libjwc_c 2010-06-15 08:53:06 jlec x11-libs/libjwc_f 2010-06-15 08:53:06 jlec dev-util/tig2010-06-15 16:15:31 jlec dev-haskell/hpc 2010-06-16 23:25:23 kolmodin sci-misc/qcad-parts 2010-06-17 17:01:44 jlec net-analyzer/zabbix-agent 2010-06-17 21:41:03 patrick net-analyzer/zabbix-frontend2010-06-17 21:41:06 patrick net-analyzer/zabbix-server 2010-06-17 21:41:06 patrick dev-util/cvs2010-06-19 01:13:16 abcd dev-util/cvs2cl 2010-06-19 01:13:17 abcd dev-util/cvsd 2010-06-19 01:13:17 abcd dev-util/cvsgraph 2010-06-19 01:13:17 abcd dev-util/cvsps 2010-06-19 01:13:18 abcd dev-util/cvsq 2010-06-19 01:13:18 abcd dev-util/cvsutils 2010-06-19 01:13:19 abcd dev-util/gitosis2010-06-19 16:14:26 arfrever dev-util/gitosis-gentoo 2010-06-19 16:24:11 arfrever Additions: sci-chemistry/makecif 2010-06-15 08:16:52 jlec dev-vcs/hgsvn 2010-06-15 08:24:17 jlec dev-libs/libjwc_c 2010-06-15 08:25:42 jlec dev-libs/libjwc_f 2010-06-15 08:29:31 jlec dev-vcs/tig 2010-06-15 16:07:36 jlec x11-themes/pulse-glass 2010-06-16 18:25:00 spatz dev-python/shiboken 2010-06-16 18:54:38 ayoy x11-plugins/pidgin-mbpurple 2010-06-17 09:00:30 fauli dev-db/kyotocabinet 2010-06-17 17:32:12 patrick dev-db/pgmemcache 2010-06-17 17:51:41 patrick sci-chemistry/bkchem2010-06-17 18:51:49 jlec media-libs/memphis 2010-06-17 19:34:25 jlec sci-biology/yass2010-06-18 05:52:46 weaver sci-biology/iedera 2010-06-18 05:53:32 weaver media-libs/pymemphis2010-06-18 07:18:36 jlec media-libs/libchamplain 2010-06-18 09:07:25 jlec sci-geosciences/gpxviewer 2010-06-18 10:14:17 jlec dev-vcs/cvs 2010-06-19 00:27:23 abcd dev-vcs/cvs2cl 2010-06-19 00:28:31 abcd dev-vcs/cvsd2010-06-19 00:30:49 abcd dev-vcs/cvsgraph2010-06-19 00:31:17 abcd dev-vcs/cvsps 2010-06-19 00:31:55 abcd dev-vcs/cvsq2010-06-19 00:32:21 abcd dev-vcs/cvsutils2010-06-19 00:32:46 abcd x11-misc/redshift 2010-06-19 09:37:15 ssuominen dev-ruby/multi_json 2010-06-19 11:35:43 flameeyes sci-electronics/voacapl 2010-06-19 11:42:24 tomjbe dev-vcs/gitosis 2010-06-19 16:05:25 arfrever dev-vcs/gitosis-gentoo 2010-06-19 16:19:58 arfrever www-apache/mod_fastcgi_handler 2010-06-19 17:08:51 hollow x11-misc/xcave 2010-06-20 10:48:14 ssuominen net-misc/googlecl 2010-06-20 13:50:14 wired x11-misc/enter 2010-06-20 21:22:49 ssuominen sys-cluster/cluster-glue2010-06-20 21:29:19 xarthisius -- Robin Hugh Johnson Gentoo Linux Developer E-Mail : robb...@gentoo.org GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 Removed Packages: dev-util/hgsvn,removed,jlec,2010-06-15 08:14:01 x11-libs/libjwc_c,removed,jlec,2010-06-15 08:53:06 x11-libs/libjwc_f,removed,jlec,2010-06-15 08:53:06 dev-util/tig,removed,jlec,2010-06-15 16:15:31 dev-haskell/hpc,removed,kolmodin,2010-06-16 23:25:23 sci-misc/qcad-parts,removed,jlec,2010-06-17 17:01:44 net-analyzer/zabbix-agent,removed,patrick,2010-06-17 21:41:03 net-analyzer/zabbix-frontend,removed,patrick,2010-06-17 21:41:06 net-analyzer/zabbix-server,removed,patrick,2010-06-17 21:41:06 dev-util/cvs,removed,abcd,2010-06-19 01:13:16 dev-util/cvs2cl,removed,abcd,2010-06-19 01:13:17 dev-util/cvsd,removed,abcd,2010-06-19 01:13:17 dev-util/cvsgraph,removed,abcd,2010-06-19 01:13:17 dev-util/cvsps,removed,abcd,2010-06-19 01:13:18 dev-util/cvsq,removed,abcd,2010-06-19 01:13:18 dev-util/cvsutils,removed,abcd,2010-06-19 01:13:19 dev-util/gitosis,removed,arfrever,2010-06-19 16:14:26 dev-util/gitosis-gentoo,removed,arfrever,2010-06-19 16:24:11 Added Packages: sci-chemistry/makecif,added,jlec,2010-06-15 08:16:52 dev-vcs/hgsvn,added,jlec,2010-06-15 08:24:17 dev-libs/libjwc_c,added,jlec,2010-06-15 08:25:42 dev-libs/libjwc_f,added,jlec,2010-06-15 08:29:31 dev-vcs/tig,added,jlec,2010-06-15 16:07:36 x11-themes/pulse-glass,added,spatz,2010-06-16 18:25:00 dev-python/shiboken,added,ayoy,2010-06-16 18:54:38 x11-plugins/pidgin-mbpurple,added,fauli,2010-06-17 09:00:30 dev-db/kyotocabinet,added,patrick,2010-06-17 17:32:12 dev-db/pgmemcache,added
Re: [gentoo-dev] Tone in Gentoo
On 06/19/2010 03:10 PM, Jorge Manuel B. S. Vicetto wrote: I can assure you that if someone goes to #gentoo-forums and tries to tell the forums team what tone should be used in that channel, we'll kindly ask the person to stop or to leave. This is one of the "public" and exposed channels and thus we have a tone with that in mind, but we're not going to set our tone according to the demands of a developer that is not even part of the team. I was not suggesting that tone in Gentoo was up to the discretion of any individual developer - neither myself, nor you, nor the head of infra/forums/etc. The tone in Gentoo is up to Gentoo. Fortunately we have a forum for deciding what Gentoo wants - we elect them annually. What would grant any non-member of a team the right to demand how the members of the team should act amongst themselves in their private room? Simple - the room belongs to Gentoo as a whole. You're certainly free not to listen to me, but I and others are free to point out that this isn't good for Gentoo. I certainly wouldn't take it upon myself to enforce the CofC, but I certainly would urge those responsible for governing the distro to do so. About the "legal right", that isn't true. There are a few misconceptions in your statement. Even though the Foundation is the body which holds the Gentoo brand, trademarks and logo, it's not the Foundation that sets the rules for joining and be part of the Gentoo Developers Community. Furthermore, being a Gentoo developer doesn't mean you can join any team you want or that you have a "right" to go to any #gentoo-* channel. In case you have any doubt, I can give you a list of quite a few channels most developers don't have access to. Your statement is partially correct - obviously if I am a stockholder in Google I can't choose to just waltz onto the corporate campus and go around as I please, merely by virtue of being a shareholder. However, a shareholder of Google certainly is able to speak out about actions within the company that they feel damage it, and their elected representatives (the board) can give power to anybody (including themselves) to waltz around and put things in order. This starts with their authority to hire and fire the CEO at whim. Ultimately, if anything contains the name "Gentoo" and represents itself as being associated with a linux distribution, then it is using a trademark owned by the Gentoo Foundation. In the end, any use of Gentoo trademarks is completely at the discretion of the Foundation. If you insist, to address the question that access lists for #gentoo-* channels can be set by Freenode (our main IRC network), you should know that the only people Freenode will listen to regarding that are the members of the Freenode Gentoo Group Contacts. The people in that group were not chosen by the Foundation nor do they respond to it. Well, this is getting a bit silly, but they'd certainly answer to a cease and desist, or those hosting their servers certainly would. It would obviously never come to that. Go ahead and try to register #microsoft-press-releases and see if being named the official contact gets you anywhere. Also, please never forget that being part of Gentoo is a "privilege" and not a "right". On that we certainly agree. It really wasn't my intention to suggest that somehow anybody was personally beholden to me. I really am just stating my opinion, as are you. As an example, even though I use my gentoo cloak online, you don't have any right to impose a behaviour into me in my private channel. Sure, I cannot, personally. However, Gentoo certainly can. At the very least I'd expect devs to generally conduct themselves in a manner where such things aren't necessary to even bring up. We have a loosely-knit community that is able to provide a reasonable product "Gentoo Linux". Let's try to avoid killing it by wanting to impose a certain "mentality" or "behaviour" into others and let's try to respect each other and learn to live in a community. Well, the whole principle of the CofC is that it imposes behaviors on those who wish to use Gentoo media, or be Gentoo staff. That said, I really don't suggest that anybody need be heavy-handed. Nor do I suggest that my personal opinion should be the one that rules Gentoo (I would say the same regarding your opinion as well). In the end that's all we're doing - you say that infra decides what happens on #gentoo-infra, and I say that they don't (well, not ultimately - certainly I'd suggest that the trustees/council should of course delegate channel moderation to the team that uses the channel, and only intervene if necessary). What I would say is that I encourage those who are in the trustees and council to recognize the importance of this issue, and I ask that they consider that tone really does matter. We elect these bodies to speak for Gentoo, and I think that this is an issue where Gentoo could stand t
Re: [gentoo-dev] New global USE flag: introspection
On Mon, Jun 21, 2010 at 4:25 AM, Brian Harring wrote: > Beyond that, the naming kind of sucks from where I'm sitting- it's a > gobject/gnome specific flag in intention, but introspection has many > meanings elsewhere that may not map cleanly there. > Well, there's nothing else in this namespace (i.e., amongst use-flags) which uses this word, and I don't see anything else that would want to use it in-tree. So, I don't see what the problem is with us taking over it :) As for confusions w.r.t. name, the use-flag descriptions exist precisely to clarify that. I personally wouldn't assume a use-flag's intention before seeing it's corresponding description. Also note that perl/ruby/python/java/javascript etc bindings will be/are using gobject-introspection[1], so this particular usage of the term will become very prevalent in the near future. 1. http://live.gnome.org/GObjectIntrospection/Users -- ~Nirbheek Chauhan Gentoo GNOME+Mozilla Team
Re: [gentoo-dev] New global USE flag: introspection
On Sun, Jun 20, 2010 at 04:14:16PM -0400, Olivier Crrrte wrote: > On Sun, 2010-06-20 at 20:12 +0530, Arun Raghavan wrote: > > I'd like to propose a new global USE-flag: introspection. > ... > > Any objections? I'll wait till Wed (June 23rd) before adding this if > > there aren't any. > > Do we really want it to be a USE flag ? I would force it on always for > everyone. Due to the direction in which GNOME is heading, it will be > required by the core desktop anyway. Use deps exist for situations like this ;) Beyond that, the naming kind of sucks from where I'm sitting- it's a gobject/gnome specific flag in intention, but introspection has many meanings elsewhere that may not map cleanly there. Anyone got a better name for it? ~harring pgpHXKyDbfSen.pgp Description: PGP signature
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-python/traits: traits-3.4.0.ebuild
On Sunday, June 20, 2010 09:55:39 Arfrever Frehtes Taifersar Arahesis wrote: > 2010-06-19 22:53:37 Mike Frysinger napisał(a): > > On Thursday, June 10, 2010 16:45:29 Arfrever Frehtes Taifersar wrote: > > > 2010-06-10 22:20:44 Nirbheek Chauhan napisał(a): > > > > On Fri, Jun 11, 2010 at 1:30 AM, Arfrever Frehtes Taifersar wrote: > > > > > 2010-06-10 21:27:40 Jeremy Olexa napisał(a): > > > > >> I see no reason to *not* add a ChangeLog entry here. > > > > > > > > > > ChangeLog entries are not required for trivial changes. > > > > > > > > A "trivial" change is fixing a typo, or a manifest problem, a missing > > > > quotation mark, etc. Anything else is not "trivial". > > > > > > > > Anything that changes how an ebuild functions, what it does, or the > > > > installed files (and/or their contents) is NOT a trivial change. > > > > > > This commit only removed some compiler warnings. > > > > mucking with CFLAGS without documentation is wrong. compiler warnings > > come and go, so a flag that was relevant one day could be completely > > extraneous the next. > > > > however, especially with strict aliasing, you arent "just fixing > > warnings", you're changing optimization behavior of gcc to workaround > > broken C code. this obviously does not fall anywhere near the "trivial" > > mark. > > > > i see you still havent fixed this, so get on it already. a bug needs to > > be opened somewhere to get the package properly *fixed* > > This problem is probably caused by bugs in Python 2, which have been fixed > in Python 3. the new information you've provided here only reinforces the fact the current code is wrong. properly document the append-flags and properly restrict it to when python-2 is being used. considering python-2 is going to be in our lives for a while, how hard is it to backport the changes in question to the headers ? presumably it's struct/union/cast shuffling in the headers. -mike signature.asc Description: This is a digitally signed message part.
[gentoo-dev] Re: New global USE flag: introspection
El lun, 21-06-2010 a las 03:05 +0530, Nirbheek Chauhan escribió: > > 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 > > > > The automagic dependency problems have all been fixed as far as I > know. Any new problems should be reported, and they will be fixed. > Great to know! :-D signature.asc Description: This is a digitally signed message part
[gentoo-dev] Re: New global USE flag: introspection
On Mon, Jun 21, 2010 at 1:07 AM, Pacho Ramos wrote: > 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. [snip] >> 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 > The automagic dependency problems have all been fixed as far as I know. Any new problems should be reported, and they will be fixed. -- ~Nirbheek Chauhan Gentoo GNOME+Mozilla Team
Re: [gentoo-dev] New global USE flag: introspection
2010/6/21 Olivier Crête : > On Sun, 2010-06-20 at 20:12 +0530, Arun Raghavan wrote: >> I'd like to propose a new global USE-flag: introspection. > ... >> Any objections? I'll wait till Wed (June 23rd) before adding this if >> there aren't any. > > Do we really want it to be a USE flag ? I would force it on always for > everyone. Due to the direction in which GNOME is heading, it will be > required by the core desktop anyway. > On the other hand, it's not just GNOME-3 which uses gtk+, atk, pango, etc. A lot of the libraries that we package are going to be used outside GNOME, and I really don't see why we should force this stuff onto them when we don't absolutely have to. -- ~Nirbheek Chauhan Gentoo GNOME+Mozilla Team
Re: [gentoo-dev] New global USE flag: introspection
On Sun, 2010-06-20 at 20:12 +0530, Arun Raghavan wrote: > I'd like to propose a new global USE-flag: introspection. ... > Any objections? I'll wait till Wed (June 23rd) before adding this if > there aren't any. Do we really want it to be a USE flag ? I would force it on always for everyone. Due to the direction in which GNOME is heading, it will be required by the core desktop anyway. -- Olivier Crête tes...@gentoo.org Gentoo Developer signature.asc Description: This is a digitally signed message part
[gentoo-dev] Re: New global USE flag: introspection
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 signature.asc Description: This is a digitally signed message part
[gentoo-dev] Re: Re: [gentoo-commits] gentoo-x86 commit in dev-python/traits: traits-3.4.0.ebuild
sön 2010-06-20 klockan 15:55 +0200 skrev Arfrever Frehtes Taifersar Arahesis: > > This problem is probably caused by bugs in Python 2, which have been fixed in > Python 3. > > $ echo 'a = True' > test.pyx > $ cython test.pyx > $ gcc -O2 -Wall -I/usr/include/python3.1 -c test.c > $ gcc -O2 -Wall -I/usr/include/python2.6 -c test.c > test.c: In function ‘inittest’: > test.c:479: warning: dereferencing type-punned pointer will break > strict-aliasing rules > test.c:479: warning: dereferencing type-punned pointer will break > strict-aliasing rules > test.c:479: warning: dereferencing pointer ‘_Py_TrueStruct.42’ does break > strict-aliasing rules > test.c:479: warning: dereferencing pointer ‘_Py_TrueStruct.42’ does break > strict-aliasing rules > test.c:479: note: initialized from here > test.c:482: warning: dereferencing pointer ‘__pyx_t_1’ does break > strict-aliasing rules > test.c:482: warning: dereferencing pointer ‘__pyx_t_1’ does break > strict-aliasing rules > test.c:482: warning: dereferencing pointer ‘__pyx_t_1’ does break > strict-aliasing rules > test.c:482: warning: dereferencing pointer ‘__pyx_t_1’ does break > strict-aliasing rules > test.c:479: note: initialized from here > Actually this makes me question the append-flag even more. Why mess with what gcc does with the code for all versions of python if it works for x version of python? And "only" for som warnings? I could have understand a bit more if it was Errors. Also why not even a comment saying? Currently as one of the users of hardened and helping Zorry out with the hardened toolchain I have seen many packages filter flags like -fPIE and -fstack-protector without a comment on why, where and how it broke, and noone remeber why. New versions comes of software and if you do not know why it broke with a cflag you cannot test if the breakage is still there. This line of code is fine and all that until you forget why you added that flag or you retire and a later maintainer of the package does not dare to touch the flag since they do not know why it was added and what will break if the remove that line of ebuild code.
[gentoo-dev] New global USE flag: introspection
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! -- Arun Raghavan http://arunraghavan.net/ (Ford_Prefect | Gentoo) & (arunsr | GNOME)
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-python/traits: traits-3.4.0.ebuild
2010-06-19 22:53:37 Mike Frysinger napisał(a): > On Thursday, June 10, 2010 16:45:29 Arfrever Frehtes Taifersar Arahesis wrote: > > 2010-06-10 22:20:44 Nirbheek Chauhan napisał(a): > > > On Fri, Jun 11, 2010 at 1:30 AM, Arfrever Frehtes Taifersar wrote: > > > > 2010-06-10 21:27:40 Jeremy Olexa napisał(a): > > > >> I see no reason to *not* add a ChangeLog entry here. > > > > > > > > ChangeLog entries are not required for trivial changes. > > > > > > A "trivial" change is fixing a typo, or a manifest problem, a missing > > > quotation mark, etc. Anything else is not "trivial". > > > > > > Anything that changes how an ebuild functions, what it does, or the > > > installed files (and/or their contents) is NOT a trivial change. > > > > This commit only removed some compiler warnings. > > mucking with CFLAGS without documentation is wrong. compiler warnings come > and go, so a flag that was relevant one day could be completely extraneous > the > next. > > however, especially with strict aliasing, you arent "just fixing warnings", > you're changing optimization behavior of gcc to workaround broken C code. > this obviously does not fall anywhere near the "trivial" mark. > > i see you still havent fixed this, so get on it already. a bug needs to be > opened somewhere to get the package properly *fixed* This problem is probably caused by bugs in Python 2, which have been fixed in Python 3. $ echo 'a = True' > test.pyx $ cython test.pyx $ gcc -O2 -Wall -I/usr/include/python3.1 -c test.c $ gcc -O2 -Wall -I/usr/include/python2.6 -c test.c test.c: In function ‘inittest’: test.c:479: warning: dereferencing type-punned pointer will break strict-aliasing rules test.c:479: warning: dereferencing type-punned pointer will break strict-aliasing rules test.c:479: warning: dereferencing pointer ‘_Py_TrueStruct.42’ does break strict-aliasing rules test.c:479: warning: dereferencing pointer ‘_Py_TrueStruct.42’ does break strict-aliasing rules test.c:479: note: initialized from here test.c:482: warning: dereferencing pointer ‘__pyx_t_1’ does break strict-aliasing rules test.c:482: warning: dereferencing pointer ‘__pyx_t_1’ does break strict-aliasing rules test.c:482: warning: dereferencing pointer ‘__pyx_t_1’ does break strict-aliasing rules test.c:482: warning: dereferencing pointer ‘__pyx_t_1’ does break strict-aliasing rules test.c:479: note: initialized from here -- Arfrever Frehtes Taifersar Arahesis signature.asc Description: This is a digitally signed message part.
[gentoo-dev] Re: Gentoo Council 2010/2011 - Voting
On 2010.06.19 20:56, Roy Bamford wrote: > Team, > > Everything is in place to allow voting in the above election commence > as planned on June 20th at 00:00:00 UTC. > > The polls will remain open until July 3rd 23:59:59 UTC. > > Your candidates are:- > betelgeuse > chainsaw > ferringb > halcy0n > jmbsvicetto > patrick > phajdan.jr > scarabeus > sping > wired > _reopen_nominations > > > Here are the rules: > > All active Gentoo developers on the roll before nominations opened > are > > eligible to vote. > > To vote login to dev.gentoo.org and run the following commands: > > 1. votify --new council201006 - This creates a new ballot in your > homedir. > 2. Edit the .ballot-council201006 file and rank the candidates. > 3. Once you're sure, run votify --verify council201006 to check > the validity of the ballot. > 4. If that goes through fine, the next and final step is to submit > your vote using votify --submit council201006 > 5. If you're stuck, use votify --help or go to #gentoo-elections > (on freenode) and ask officials for help. > > Votes that are not submitted before the poll closes will not be > counted. > > Good luck and thank you for all your votes. > > -- > Regards, > > Roy Bamford [snip] Team, The problem with the ballot has now been fixed - thank you to those members of the electorate that drew it to our attention. The above rules and timescales still apply. The elections team determined that the voting period should not be extended. -- Regards, Roy Bamford (Neddyseagoon) a member of gentoo-ops forum-mods trustees elections
[gentoo-dev] My Council manifest
On 19.6.2010 21.56, Roy Bamford wrote: > Team, > > Everything is in place to allow voting in the above election commence > as planned on June 20th at 00:00:00 UTC. > I put an initial manifesto here: http://dev.gentoo.org/~betelgeuse/manifesto-2010.html I will take a second glance on it once I get back from Barcelona tomorrow. Regards, Petteri
[gentoo-dev] Last rites: x11-misc/xvidcap
# Markos Chandras (20 Jun 2010) # Bundles ffmpeg copy, doens't work with systems' ffmpeg # Bug #258042. Replacement is media-video/recordmydesktop # Pending removal in 2010-07-20 x11-misc/xvidcap -- Markos Chandras (hwoarang) Gentoo Linux Developer Web: http://hwoarang.silverarrow.org pgp6VwwcVnTlN.pgp Description: PGP signature
[gentoo-dev] new warnings to catch from gcc in portage
the newer fortify/security work in gcc provides some nice checks which portage doesnt currently flag. those are: ": warning: array subscript is below array bounds$" ": warning: array subscript is above array bounds$" ": warning: attempt to free a non-heap object" ": warning: .* called with .*bigger.* than .* destination buffer$" ": warning: call to .* will always overflow destination buffer$" this should catch the kind of checks where people check for pointer math overflow but dont realize that gcc optimizes it away: ": warning: assuming pointer wraparound does not occur when comparing " these tend to be typos in code: ": warning: hex escape sequence out of range$" ": warning: [^ ]*-hand operand of comma .*has no effect$" these too are typos/thinkos involving NULL instead of a value of 0, or misordering of arguments: ": warning: converting to non-pointer type .* from NULL" ": warning: NULL used in arithmetic$" ": warning: passing NULL to non-pointer argument" these tend to be thinkos which result in incorrect behavior: ": warning: the address of [^ ]* will always evaluate as" ": warning: the address of [^ ]* will never be NULL" think "char foo[1234]" and later doing "if (foo) ..." i cant see this being valid: ": warning: too few arguments for format" or trying to return addresses to function locals: ": warning: reference to local variable .* returned" ": warning: returning reference to temporary" ": warning: function returns address of local variable" -mike signature.asc Description: This is a digitally signed message part.