public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
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 11:59:02 +0100	[thread overview]
Message-ID: <20091202115902.162d696f@gentoo.org> (raw)
In-Reply-To: <200912020957.40895.scarabeus@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 754 bytes --]

Hi,

Tomáš Chvátal <scarabeus@gentoo.org>:
> > 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

 Microsoft Windows is standard software, too....you want to use it?  And
if an ebuild uses EAPI 3 it will fail badly, while it isn't too old.  A
sane assumption is that EAPI 3 will at least contain all features from
EAPI 2 with very few adjustments to existing syntax and behaviour if at
all.

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 --]

  parent reply	other threads:[~2009-12-02 10:59 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
2009-12-02 10:46     ` Fabian Groffen
2009-12-05  8:59       ` Hans de Graaff
2009-12-02 10:59     ` Christian Faulhammer [this message]
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=20091202115902.162d696f@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