Currently, src_compile looks like this in ebuild.sh: if [ -x ./configure ]; then econf emake || die "emake failed" fi This is fine for a lot of ebuilds, but there is a good number of ebuilds where it would be nice if the emake part would fire off if there were a GNUmakefile, makefile, or Makefile (these are the three files that GNU make looks for, in that order). Basically, moving the emake out of the check for configure. This would enable packages that are similar to app-text/tree that don't use autoconf, but simply provide a makefile to avoid providing an ebuild-specific src_compile.
This would be best: if [ -x ./configure ]; then econf || die "econf failed" fi if [ -f Makefile -o -f GNUmakefile -o -f makefile ]; then emake || die "emake failed" fi
Thanks Aron. That would be ideal portage devs. ^^^^
This breaks with packages that have a Makefile that's only used for `make install` (e.g. sys-apps/man-pages)
sys-apps/man-pages should just supply an empty src_compile function I think. That is a pretty unusual case. The more general case (that is, probably autoconf, followed in frequency by simple makefiles that are used for compiling and installing) should be the one supported by the generic src_compile in my opinion.
FWIW, I agree with Mr_Bones_, man-pages should just supply an "empty" function: src_compile() { true # nothing to do, override default src_compile }
This is in _pre9, and I changed man-pages so that it doesn't explode.
