On Tue, Dec 05, 2006 at 01:37:42AM +0100, Milosz Derezynski wrote: > OK this is the other bug (i was just about to write something about being > out of sync heh). > Soo, first of all this has been fixed since we're using a different system > to create the translations now, but furthermore I would like to point out > that the code that produced the warningns (the code in the intl/ directory > IIRC) is/was not part of BMP, so fixing this on _our_ side by removing the > -std=c99 argument would, if you want to put it on the sharp edge, constitute > a workaround and i'd rather propagate this further upstream so that either > they (GNU i guess erm, yeah GNU intltool) state that their code isn't C99 > compliant (which would be a little problematic for the case that your app > contains C99 code), or they fix it to _be_ C99 compliant but in either case > i don't see why BMPx should remove a build flag which is perfectly valid for > its own code.
I'm not playing the finger pointing game here - the buggy code may have been sent via fax from a monkey being held prisoner on the space station, but it is included in the bmpx package and is therefore a bug in that package. I see that there's an intltool package in Debian - perhaps you could build-depend on that instead of building your own copy? If possible, that would prevent future issues like this. You don't have to take my patch and I honestly don't care how you choose to fix it. You are the maintainer (I'm assuming), so I'd hope you'd know better than me. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
