From: | "Tomáš Chvátal" <scarabeus@g.o> | ||
---|---|---|---|
To: | gentoo-dev@l.g.o | ||
Subject: | Re: [gentoo-dev] Re: RFC: ruby-ng.eclass - new eclass for ruby-based packages | ||
Date: | Wed, 02 Dec 2009 08:58:20 | ||
Message-Id: | 200912020957.40895.scarabeus@gentoo.org | ||
In Reply to: | [gentoo-dev] Re: RFC: ruby-ng.eclass - new eclass for ruby-based packages by Christian Faulhammer |
1 | Dne středa 02 Prosinec 2009 09:51:25 Christian Faulhammer napsal(a): |
2 | > At the moment I don't remember for what reason exactly, but we renamed |
3 | > the PATCHES variable to EBZR_PATCHES in bzr.eclass. You should do |
4 | > something similar. |
5 | No reason to rename it if they use base_src_prepare |
6 | > |
7 | > EXPORT_FUNCTIONS src_unpack src_prepare src_configure src_compile |
8 | > src_test src_install pkg_setup |
9 | > |
10 | > case ${EAPI} in |
11 | > 2) ;; |
12 | > *) |
13 | > die "Unsupported EAPI=${EAPI} for ruby-ng.eclass" |
14 | > esac |
15 | > |
16 | > The sense of this I don't understand. You should not restrict EAPI |
17 | > like this. |
18 | > |
19 | > V-Li |
20 | > |
21 | Why not. Quite standart way. |
22 | 19 case ${EAPI:-0} in |
23 | 20 2) : ;; |
24 | 21 *) DEPEND="EAPI-TOO-OLD" ;; |
25 | 22 esac |
26 | |
27 | Tom |
File name | MIME type |
---|---|
signature.asc | application/pgp-signature |
Subject | Author |
---|---|
Re: [gentoo-dev] Re: RFC: ruby-ng.eclass - new eclass for ruby-based packages | Fabian Groffen <grobian@g.o> |
[gentoo-dev] Re: RFC: ruby-ng.eclass - new eclass for ruby-based packages | Christian Faulhammer <fauli@g.o> |
Re: [gentoo-dev] Re: RFC: ruby-ng.eclass - new eclass for ruby-based packages | Hans de Graaff <graaff@g.o> |