From: Christian Faulhammer <fauli@gentoo.org>
To: Gentoo Development <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Re: RFC: ruby-ng.eclass - new eclass for ruby-based packages
Date: Wed, 2 Dec 2009 09:51:25 +0100 [thread overview]
Message-ID: <20091202095125.2e300c55@gentoo.org> (raw)
In-Reply-To: <1259737917.26974.8.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 866 bytes --]
Hans de Graaff <graaff@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/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-12-02 8:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 7:11 [gentoo-dev] RFC: ruby-ng.eclass - new eclass for ruby-based packages Hans de Graaff
2009-12-02 8:51 ` Christian Faulhammer [this message]
2009-12-02 8:57 ` [gentoo-dev] " Tomáš Chvátal
2009-12-02 10:46 ` Fabian Groffen
2009-12-05 8:59 ` Hans de Graaff
2009-12-02 10:59 ` Christian Faulhammer
2009-12-05 9:32 ` Hans de Graaff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091202095125.2e300c55@gentoo.org \
--to=fauli@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox