Hi,
Oh, this is all fine for _GStreamer_, but bad for _GNOME_, because
this sends away potencial GNOME contributors since it's simply too
difficult to build it. Sorry to be so blunt, but I think it was selfish
of the GStreamer project to have -Werror in the makefiles.
Two notes:
- -Werror
On Fri, 2005-11-11 at 14:24 +0100, Thomas Vander Stichele wrote:
Two notes:
- -Werror is only enabled for CVS; releases have it disabled by default.
-
http://gstreamer.freedesktop.org/data/doc/gstreamer/head/faq/html/chapter-cvs.html#werror
also shows how easy it is to override the flags.
Hey,
On Fri, 2005-11-11 at 16:20 +, Ross Burton wrote:
I'm guessing that Gustavo thought that -Werror was enabled in the
releases, which everyone agrees is a bad idea (new compilers warn about
code in interesing ways). I agree that using strict compile flags in
development is a good
Currently, a11y is not enabled by default in GNOME, as it has a
performance cost (CPU and memory usage).
But that means that there's a huge amount of code that isn't being
exercised by most testers and developers.
So here's a (possibly crazy) suggestion: during development releases,
enable a11y
fre, 11,.11.2005 kl. 12.20 -0500, skrev David Malcolm:
Currently, a11y is not enabled by default in GNOME, as it has a
performance cost (CPU and memory usage).
But that means that there's a huge amount of code that isn't being
exercised by most testers and developers.
So here's a
On Fri, 2005-11-11 at 12:20 -0500, David Malcolm wrote:
So here's a (possibly crazy) suggestion: during development releases,
enable a11y by default, and during stable releases, disable it by
default. That way people running jhbuild, GARNOME etc would be running
all of the a11y code, and any
On 11/11/05, Federico Mena Quintero [EMAIL PROTECTED] wrote:
On Fri, 2005-11-11 at 12:20 -0500, David Malcolm wrote:
So here's a (possibly crazy) suggestion: during development releases,
enable a11y by default, and during stable releases, disable it by
default. That way people running
Le vendredi 11 novembre 2005 à 12:00 -0700, Elijah Newren a écrit :
On 11/11/05, Federico Mena Quintero [EMAIL PROTECTED] wrote:
On Fri, 2005-11-11 at 12:20 -0500, David Malcolm wrote:
So here's a (possibly crazy) suggestion: during development releases,
enable a11y by default, and
On 11/11/05, Vincent Untz [EMAIL PROTECTED] wrote:
FWIW, it effectively disables the reduced resources mode in metacity
(except that the minimization animation remains off) which would
result in part of Metacity being untested.
Is there any reason for this behavior?
It was done before I
On 11/11/05, Claudio Saavedra [EMAIL PROTECTED] wrote:
On Fri, 2005-11-11 at 12:00 -0700, Elijah Newren wrote:
[...]
FWIW, it effectively disables the reduced resources mode in metacity
(except that the minimization animation remains off) which would
result in part of Metacity being
On Gwe, 2005-11-11 at 20:23 +0100, Claudio Saavedra wrote:
making GNOME crash. Instead of making this changes a *must* for all the
people involved with the HEAD code, why not better making more noise
(mailing lists, p.g.o, etc.) so everyone know that exists some areas of
the desktop
On Fri, 2005-11-11 at 12:00 -0700, Elijah Newren wrote:
FWIW, it effectively disables the reduced resources mode in metacity
(except that the minimization animation remains off) which would
result in part of Metacity being untested.
So what you want is a tool to test code coverage, and an
On Fri, 2005-11-11 at 20:23 +0100, Claudio Saavedra wrote:
Considering that there are pros and cons, why force all developers,
contributors and testers to take part in this?
If you want a stable development platform, use the stable series, not
CVS HEAD.
When things start breaking in the basic
Dear hackers of GNOME,
Vincent announced this the other day:
http://mail.gnome.org/archives/desktop-devel-list/2005-November/msg6.html
And there was a discussion of how to implement this plan.
Glib now supports setting an environment variable, G_DEBUG=fatal_criticals.
Doing this will
On 11/11/05, Luis Villa [EMAIL PROTECTED] wrote:
On 11/11/05, Federico Mena Quintero [EMAIL PROTECTED] wrote:
Remember, on January 1st 2006 this change will happen automatically, and
things that have not been fixed will start crashing all over the place.
So fix them now.
In the meantime,
On 11/11/05, Federico Mena Quintero [EMAIL PROTECTED] wrote:
On Fri, 2005-11-11 at 12:18 -0700, Elijah Newren wrote:
It was done before I got involved with Metacity. You'd have to ask
Bill, Havoc, or Rob, or maybe all three and hope that they all
remember enough pieces to get the whole
[Dropping the devel-announce-list cc until we have an announcement
rather than discussion]
On 11/11/05, Luis Villa [EMAIL PROTECTED] wrote:
On 11/11/05, Elijah Newren [EMAIL PROTECTED] wrote:
Why a keyword over say the status whiteboard? I don't imagine that
people will widely search for
On 11/11/05, Luis Villa [EMAIL PROTECTED] wrote:
On 11/11/05, Elijah Newren [EMAIL PROTECTED] wrote:
I dunno. Anyone have good suggestions? critical-warning-crasher maybe?
Also, as an aside,
http://bugzilla.gnome.org/reports/boogle.cgi?query=-CRITICAL; seems
to be fairly good at
[Cc:-ing desktop-devel, and with my Flame-Resistant,
I-Can't-Believe-It's-Not-Asbestos jacket on]
Hi all.
In order to let others know how's the status of GNOME Dictionary
Breaking is progressing (and in order to force myself hacking on it
regularly ;-)), I'm sending the
Not So Weekly
Hi,
On 11/11/05, Emmanuele Bassi [EMAIL PROTECTED] wrote:
In order to let others know how's the status of GNOME Dictionary
Breaking is progressing (and in order to force myself hacking on it
regularly ;-)), I'm sending the
Not So Weekly Status Report on GNOME Dictionary
Containing
20 matches
Mail list logo
