Hans de Graaff <gra...@gentoo.org>: > The eclass itself is attached to this message and here: > http://git.overlays.gentoo.org/gitweb/?p=proj/ruby-scripts.git;a=blob;f=ruby-ng-testbed/eclass/ruby-ng.eclass;h=ce9a37440600c7913a21b5780a18b5e8dd9d712f;hb=HEAD
At the moment I don't remember for what reason exactly, but we renamed the PATCHES variable to EBZR_PATCHES in bzr.eclass. You should do something similar. EXPORT_FUNCTIONS src_unpack src_prepare src_configure src_compile src_test src_install pkg_setup case ${EAPI} in 2) ;; *) die "Unsupported EAPI=${EAPI} for ruby-ng.eclass" esac The sense of this I don't understand. You should not restrict EAPI like this. V-Li -- Christian Faulhammer, Gentoo Lisp project <URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode <URL:http://gentoo.faulhammer.org/>
signature.asc
Description: PGP signature