Upstream is aware of it and should fix everything for evolution 2.30.
In the meantime, add a (nasty) hack so that we don't end up with
undefined symbols.
Reorder Makefile while here and tweak dependencies.
ok jasper@
As advertised, it is a hack (that abuses -Wl,--as-needed for plugins)
but it speeds up evolution startup by a factor or 9 (yes...).
While here, re-enable the org.gnome.mail.account plugin which became
usable in the process and s/LOCALBASE/TRUEPREFIX.
ok jasper@
(${SCHEMAS_INSTDIR}). Granted this take one or two more seconds to
install the -plugins subpackage but it allows us to use the generic
gconf-2 goo in PLIST-plugins.
While here, regen wantlib and lib_depends.
ok jasper@
* split in 2 packages:
-main ===> evolution+base plugins
-plugins ===> plugins part of the "standard" bundle
This makes more sense than previous tweak and preserves ressources.
* disable the mail-account-disable plugin by default (you can still
enable it from the plugins preferences) ; there is something not
quite right about it that makes right-clicking on a folder very
slow ; it's beeing investigated but for now, evolution is slow
enough...
* fix some hardcoded paths in the antispam plugins
* import 2 patches from pkgsrc and FreeBSD which fixes some obvious
issues
* evolution needs gnome-icon-theme to build
* remove the rpath related stuff from LDFLAGS which prevented
building on macppc ; the plugins link with '-rpath $(plugindir)' so
it should not be needed anymore
please CONTACT ME if you see any regression (in which case bernd@ can
spank me for free)
ok jasper@
gtk-update-icon-cache is part of gtk+2: adding gtk+2 to run_depends just
to update the icon cache (which only gtk apps can use) is overkill to
say the least!
As from now, each time icons are installed under %D/share/icons, we try
to execute gtk-update-icon-cache and if it is not there, we just ignore
the error.
What it means is that if you have gtk+2 installed, then it'll run fine
and your apps will be able to use the cache. Otherwise, it will silently
fails which is fine since it means none of your apps would have been
able to take advantage of the cache anyway.
discussed with jasper@
- explicitly disable some stuff
- enable base plugins
"no objections here" martynas@
note, there is are some issues left, but this will be fixed shortly.
