GNOME Bugzilla – Bug 95617
Should not generate projects that depend on gnome-common
Last modified: 2004-12-22 21:47:04 UTC
IMO gnome-common is questionable even for modules that are part of GNOME, but it's _definitely_ bad for Glade to make third-party projects depend on it. The "interface" presented by gnome-common is in no way guaranteed, stable, maintained, locked-down, reliable. It can change tomorrow and break everybody's project. Glade should not use any of the rather useless m4 macros in gnome-common, and should just copy some simple/generic autogen.sh that comes with Glade into the project. Or just run auto* manually, or use autoreconf. (Or rely on Anjuta for this type of stuff and keep Glade as a glade file editor.)
Yes, we don't really need to make apps depend on it. (Though its status is a little confusing - is it part of GNOME or not?)
Should be fixed in CVS. We use our own autogen.sh now, and don't use GNOME_COMPILE_WARNINGS.