[gstreamer-bugs] [Bug 560442] GNOME Goal: Remove deprecated GLib symbols

GStreamer (bugzilla.gnome.org) bugzilla-daemon at bugzilla.gnome.org
Wed Nov 12 08:44:24 PST 2008


If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=560442

  GStreamer | don't know | Ver: HEAD CVS

Luis Menina changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |UNCONFIRMED




------- Comment #2 from Luis Menina  2008-11-12 16:44 UTC -------
As there's an awful *lot* of modules to check (the whole GNOME stack, and some
external dependencies too), I'm using egrep to find the symbols, doing some
kind of static analysis. Doing so makes easier for newcommers to contribute to
the GNOME Goals: they don't need to compile a module to know wether a module
uses deprecated symbols or not. I can also tell them which module they can fix,
without building the whole GNOME stack myself.

Static analysis is much also much faster: calling 'jhbuild update' and then
egrep to find deprecated symbols allows me to easily know the state of each
module. Compare this to the time required to build the whole GNOME stack... 

I understand that removing "false positives" (comments, calls in dead code) can
be seen as tedious and useless, because it's not a "bug". But doing so will
make subsequent checks easier, making GNOME 3.0 transition smoother (this goal
concerns GLib, but the same will be applied to GTK, GDK, and gdk-pixbuf in
another GNOME Goal).

The only workaround I could see is to use the build brigade to compile GNOME
with deprecated symbols disabled by default, and have them notify people when
the build breaks. But results may vary, according to build options, and it
become harder to involve people that way...

In conclusion, if your tests are neither used nor distributed, why don't you
drop them ? SVN will keep them for you in case you need to pick some stuff from
there. But is there really a good reason to keep them around ?


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=560442.




More information about the Gstreamer-bugs mailing list