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 605718 - Remove Bonobo usage
Remove Bonobo usage
Status: RESOLVED WONTFIX
Product: Gnumeric
Classification: Applications
Component: General
git master
Other All
: Normal enhancement
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks: 588321
 
 
Reported: 2009-12-30 08:03 UTC by Javier Jardón (IRC: jjardon)
Modified: 2009-12-30 09:19 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Javier Jardón (IRC: jjardon) 2009-12-30 08:03:46 UTC 
Bonobo is deprecated and will be removed for GNOME 3.

I am aware that Gnumeric is not an official part of GNOME but it would be more than welcome to clean up the codebase, also for GNOME distributors.
D-Bus (and other stuff) is available nowadays.

For automated statistics see http://www.gnome.org/~fpeters/299.html .
Comment 1 Andreas J. Guelzow 2009-12-30 08:32:03 UTC 
Please wait with filing this bug until GNOME 3 is at least at the horizon. Gnumeric currently works with gtk+ 2.12.
Comment 2 André Klapper 2009-12-30 08:45:43 UTC 
This is not INVALID, but a valid enhancement request.
Comment 3 Andreas J. Guelzow 2009-12-30 08:50:21 UTC 
okay, then WONTFIX
Comment 4 Jean Bréfort 2009-12-30 08:53:36 UTC 
Anyway, upcoming gnumeric-1.10.0 does NOT use bonobo when built with default settings.
Comment 5 Andreas J. Guelzow 2009-12-30 09:02:07 UTC 
In fact, even for the gnumeric currently in debian unstable:

[aguelzow@kirkman ~]$ ldd `which gnumeric` | fgrep bonobo | wc
      0       0       0

while on the other hand 
[aguelzow@kirkman ~]$ ldd `which evolution` | fgrep bonobo | wc
      3      12     202


You really should look at the your core applications first.
Comment 6 André Klapper 2009-12-30 09:19:52 UTC 
(In reply to comment #5)
> You really should look at the your core applications first.

We did, and as the situation is quite clear now we started warning also non-core apps to get ready if they want to. :)