Eugen Dedu a écrit :
Eugen Dedu wrote:Julien Puydt wrote:Eugen Dedu a écrit :Make the evolution code a plugin... the basic framework is here... we even already have a plugin loader!Luca Capello wrote:Hi Julien! On Sun, 07 Jun 2009 18:40:43 +0200, Julien Puydt wrote:Luca Capello a écrit :1) Ekiga requires too much disk space:[...]I would like a minimal version with no GNOME libraries (Bonobo &Co.), just Opal, PTlib and the minimum required GTK+, full stop. MayI remind you that the Openmoko GTA02 Neo FreeRunner has 256MB of flash? :-(It *is* possible to disable the evolution support -- it looks like it's the culprit behind most of the deps.Eugen, should I officially ask for a ekiga-gtk-only package?A similar report exists on debian bugzilla, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520830 . The best solution is to add runtime detection (used by those who installed it, not used by the others), as shown here:"what you suggest ("ekiga: Dependancy on evolution-data-server should be removed or moved to additional package") should be possible after addingruntime detection of evolution-data-server to Ekiga." Could that be done in ekiga?I made a bug report, not to forget it: http://bugzilla.gnome.org/show_bug.cgi?id=586147Julien has just fixed it on master: evolution (and kde, kab etc.) are plugins now. Julien, could you explain how this affects building (if it does affect)? Are these plugins generated as .so or what? Are they always built or what?
Well, it's still possible not to build those pieces of code with the usual --disable switches : that didn't change.
The difference is that now, when it's built, it's possible to package ekiga and those pieces separately ; the ekiga executable doesn't have those features (and doesn't link to the libs they depend on).
Snark