From: | Christian Faulhammer <fauli@g.o> | ||
---|---|---|---|
To: | Gentoo Development <gentoo-dev@l.g.o> | ||
Subject: | [gentoo-dev] Re: RFC: ruby-ng.eclass - new eclass for ruby-based packages | ||
Date: | Wed, 02 Dec 2009 08:51:49 | ||
Message-Id: | 20091202095125.2e300c55@gentoo.org | ||
In Reply to: | [gentoo-dev] RFC: ruby-ng.eclass - new eclass for ruby-based packages by Hans de Graaff |
1 | Hans de Graaff <graaff@g.o>: |
2 | |
3 | > The eclass itself is attached to this message and here: |
4 | > 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 |
5 | |
6 | At the moment I don't remember for what reason exactly, but we renamed |
7 | the PATCHES variable to EBZR_PATCHES in bzr.eclass. You should do |
8 | something similar. |
9 | |
10 | EXPORT_FUNCTIONS src_unpack src_prepare src_configure src_compile |
11 | src_test src_install pkg_setup |
12 | |
13 | case ${EAPI} in |
14 | 2) ;; |
15 | *) |
16 | die "Unsupported EAPI=${EAPI} for ruby-ng.eclass" |
17 | esac |
18 | |
19 | The sense of this I don't understand. You should not restrict EAPI |
20 | like this. |
21 | |
22 | V-Li |
23 | |
24 | -- |
25 | Christian Faulhammer, Gentoo Lisp project |
26 | <URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode |
27 | |
28 | <URL:http://gentoo.faulhammer.org/> |
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 | "Tomáš Chvátal" <scarabeus@g.o> |