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 557889 - Ekiga::Runtime isn't very good
Ekiga::Runtime isn't very good
Status: RESOLVED WONTFIX
Product: ekiga
Classification: Applications
Component: Engine
GIT master
Other All
: Normal normal
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2008-10-25 19:15 UTC by Snark
Modified: 2020-06-06 16:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Snark 2008-10-25 19:15:25 UTC 
I don't like it :  it's in the ServiceCore, but we would like to have it available from threads more readily since it's its main mission.

It is officially independant from glib, but there are places where the code expects a glib mainloop anyway :
- in the avahi code ;
- in the XCAP::Core code (libsoup implementation) ;
- and of course the gtk+ code.

I don't know what to do about it, but it's annoying.
Comment 1 Snark 2009-03-23 20:39:46 UTC 
I modified the way the runtime works -- it isn't in the service core anymore as an object. It is in a widely accessible namespace (and yes, it uses static variables...).

It's still not very good, but it makes clearer code.
Comment 2 André Klapper 2020-06-06 16:29:01 UTC 
Ekiga is not under active development anymore:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/273

Ekiga saw its last release 7 years ago. The last code commits were 4 years ago.

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (and transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active Ekiga development again in the future.