When we moved from emacs 22 to 23, the default dependencies seem to have become much much bigger. I typically run with fairly few PKG_OPTIONS compared to default, but I do have default options 'cups' (because I think that if I run cups, I really need to do that to make everything work - maybe I'm wrong). Here's the comparison: emacs-22.3nb5: perl>=5.0 jpeg>=7 tiff>=3.6.1 png>=1.2.4 emacs 23, other hand, by default pulls in librsvg and gtk2+, which means: librsvg-2.26.0: glib2>=2.12.0 libgsf>=1.13.3 libxml2>=2.6.2 pango>=1.6.0 fontconfig>=2.4.2 freetype2>=2.1.8 cairo>=1.2.0 libcroco>=0.6.1 gtk2+>=2.6.0 gtk2+: python25>=2.5.1 cups>=1.1.19nb3 png>=1.2.4 tiff>=3.6.1 jpeg>=7 fontconfig>=2.4.2 freetype2>=2.1.8 shared-mime-info>=0.15 glib2>=2.21.3 atk>=1.13.0 pango>=1.20.0 cairo>=1.6.0 My proposal is to change PKG_SUGGESTED_OPTIONS to remove svg gtk (and thus turn on xaw) dbus dbus only includes dbus and expat. But, it's not clear that dbus support in emacs is useful for much, and people who want it are likely quite capable of PKG_OPTIONing it on. I use emacs on machines that are servers. I do want X11 support, but I don't want to pull in all of gtk2+ and the GNOME2 structured file library. (Perhaps we should have emacs-gtk, or perhaps this is another argument for multiple option-flavors build being available in the default binary set.) The real question is how our users are best served. My best guess is that emacs users are more on the traditionalist side and that the default build ought to be smaller.
Description: PGP signature