On 02-12-2009 09:57:37 +0100, Tomáš Chvátal wrote:
> Dne středa 02 Prosinec 2009 09:51:25 Christian Faulhammer napsal(a):
> > 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.
> No reason to rename it if they use base_src_prepare
> >
> > 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
> >
> Why not. Quite standart way.
> 19 case ${EAPI:-0} in
> 20 2) : ;;
> 21 *) DEPEND="EAPI-TOO-OLD" ;;
> 22 esac
I guess you better add a section for known eapis that are too old to
your liking, and use the *) section for an oops message saying you don't
know about ${EAPI} yet, and to please file a bug.
--
Fabian Groffen
Gentoo on a different level
