GNOME Bugzilla – Bug 595353
evince must ship gconf-2.m4 file with itself
Last modified: 2009-11-01 11:02:24 UTC
Created attachment 143270 [details] gconf-2.m4 evince normally builds and works if gconf hasn't been installed, but aclocal fails without gconf-2.m4 macros. Evince package must include thit file.
No. You need to install the gconf devel package to run autogen, so gconf.m4 can be found by aclocal. *Tarball* builds otoh work fine without gconf.
(In reply to comment #1) > No. You need to install the gconf devel package to run autogen, so gconf.m4 can > be found by aclocal. *Tarball* builds otoh work fine without gconf. Why??? I'm xfce user, i don't want to install gconf and any other shit i don't need, but i need to run autogen on every version of evince (distribution-specific patches). evince' package contains gtk-doc.m4, gnome-doc-utils.m4, some libtool's m4 files therefore i can run autogen without gtk-doc, gnome-doc-utils or libtool installed, so why i need to install gconf for that? Why putting 1.5kb-file into package is a trouble? PS My distro is source-based, there is no devel packages :)
The *tarballs* contain these m4 files; they are *not* in git. To build from git you just need to install gnome-doc-utils, intltool, libtool, gtk-doc and gconf development packages. These m4 files are copied into m4/ by the various -ize tools (gnome-doc-prepare, intltoolize, libtoolize, gtkdocize) that are run by gnome-autogen.sh; so *arguably* gconf could have a similar tool that copied its m4 file in, and gnome-autogen.sh would run that tool when it detects AM_GCONF_SOURCE_2 macro in configure.ac. These would then be gconf and/or gnome-common RFEs thowever, not an evince bug. (NB: which distro is this, why do the distro patches require re-running autogen, and why can't these distro patches be submitted upstream?)
(In reply to comment #3) > The *tarballs* contain these m4 files; they are *not* in git. hmm... okey... > To build from git you just need to install gnome-doc-utils, intltool, libtool, > gtk-doc and gconf development packages. These m4 files are copied into m4/ by > the various -ize tools (gnome-doc-prepare, intltoolize, libtoolize, gtkdocize) > that are run by gnome-autogen.sh; so *arguably* gconf could have a similar tool > that copied its m4 file in, and gnome-autogen.sh would run that tool when it > detects AM_GCONF_SOURCE_2 macro in configure.ac. These would then be gconf > and/or gnome-common RFEs thowever, not an evince bug. okey, i'll write them about this. > (NB: which distro is this, why do the distro patches require re-running > autogen, and why can't these distro patches be submitted upstream?) Gentoo. This is the part of emerge log: >>>> Emerging (1 of 1) app-text/evince-2.27.90 from gnome >... > * Fixing OMF Makefiles ... [ ok ] > * Running elibtoolize in: evince-2.27.90 > * Applying portage-2.2.patch ... > * Applying sed-1.5.6.patch ... > * Applying as-needed-2.2.6.patch ... > * Applying evince-0.7.1-display-menu.patch ... [ ok ] > * Applying evince-2.27.4-smclient-configure.patch ... [ ok ] > * Running eautoreconf in '/var/tmp/portage/app-text/evince-2.27.90/work/evince-2.27.90' ... >... I don't know has evince-2.27.4-smclient-configure.patch been sent upstream. I don't know are all of these needed. I'm stupid user :)
Turns out that evince-2.27.4-smclient-configure.patch is supposed to fix bug 590174.
*** Bug 600297 has been marked as a duplicate of this bug. ***