After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 95617 - Should not generate projects that depend on gnome-common
Should not generate projects that depend on gnome-common
Status: RESOLVED FIXED
Product: glade-legacy
Classification: Deprecated
Component: general
unspecified
Other other
: Normal major
: ---
Assigned To: Damon Chaplin
Damon Chaplin
Depends on:
Blocks:
 
 
Reported: 2002-10-12 15:29 UTC by Havoc Pennington
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Havoc Pennington 2002-10-12 15:29:14 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.)
Comment 1 Damon Chaplin 2002-10-15 23:47:50 UTC
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?)
Comment 2 Damon Chaplin 2002-11-02 16:40:15 UTC
Should be fixed in CVS. We use our own autogen.sh now, and don't use
GNOME_COMPILE_WARNINGS.