After patching monotone as described in bug #380257 comment #8, monotone still fails to build for me because it cannot compile the emacs files the ebuild expect: * Compiling GNU Emacs Elisp files ... >>Error occurred processing *.el: File error (("Opening input file" "no such file or directory" "/var/tmp/portage/dev-vcs/monotone-1.0/work/monotone-1.0/contrib/*.el")) * elisp-compile: batch-byte-compile failed [ !! ] * ERROR: dev-vcs/monotone-1.0 failed (compile phase): * (no error message) * * Call stack: * ebuild.sh, line 56: Called src_compile * environment, line 2493: Called die * The specific snippet of code: * elisp-compile *.el || die; Makes sense, as there are really no files matching that glob. There is a single *.el file in the Attic subdirectory of that dir. The monotone revision log has this to say about it: Revision: b0994cc85716cfdf5f19f0c525f8570dcbcf0435 Parent: f401a544f455bdcc8452ce9c0dd4934a543dbf57 Author: Richard Levitte <richard@levitte.org> Date: 08.03.2011 13:14:54 Branch: net.venge.monotone Changelog: * contrib/monotone-nav.el: Move to contrib/Attic/, as it seems quite antique. It supposedly uses direct database queries, which shouldn't be necessary with the automate interface, and it refers to a elisp module monotone which is nowhere to be found. Changes against parent f401a544f455bdcc8452ce9c0dd4934a543dbf57 renamed contrib/monotone-nav.el to contrib/Attic/monotone-nav.el So I guess the emacs USE flag should simply be dropped. Setting USE=-emacs makes the compile phase succeed, just to dump me to the next error in the install phase, but that will be another bug report.
Thank you for report. USE flag and relevant code was dropped. Fixed.
