public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Tomáš Chvátal" <scarabeus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: RFC: ruby-ng.eclass - new eclass for ruby-based packages
Date: Wed, 2 Dec 2009 09:57:37 +0100	[thread overview]
Message-ID: <200912020957.40895.scarabeus@gentoo.org> (raw)
In-Reply-To: <20091202095125.2e300c55@gentoo.org>

[-- Attachment #1: Type: Text/Plain, Size: 731 bytes --]

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

Tom

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2009-12-02  8:58 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 ` [gentoo-dev] " Christian Faulhammer
2009-12-02  8:57   ` Tomáš Chvátal [this message]
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=200912020957.40895.scarabeus@gentoo.org \
    --to=scarabeus@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