public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 1/5] out-of-source-utils.eclass: New utility eclass
Date: Mon, 02 Jan 2023 13:24:25 +0100	[thread overview]
Message-ID: <1cbd5bb92bc498f5cbed7a281ad610a5a36b4986.camel@gentoo.org> (raw)
In-Reply-To: <ubknhe1ai@gentoo.org>

On Mon, 2023-01-02 at 10:25 +0100, Ulrich Mueller wrote:
> > > > > > On Sun, 01 Jan 2023, Michał Górny wrote:
> 
> > +case ${EAPI} in
> > +	6|7|8) ;;
> > +	*) die "${ECLASS}: EAPI ${EAPI} unsupported."
> 
> Are you sure that this will work without the final ;; terminator?
> (Bash documentation says that a terminator is mandatory.)

Interesting enough, it does work.

> Apart from that, I'd suggest to use the standard clause as in other
> eclasses:
> 
> 	*) die "${ECLASS}: EAPI ${EAPI:-0} not supported" ;;
> 

Actually, this is what app-vim/gentoo-syntax spews by default.  I guess
I need to change it.

Anyway, replaced by your snippet.  I suppose it's fine if I don't
resubmit the batch for this change.

-- 
Best regards,
Michał Górny



      reply	other threads:[~2023-01-02 12:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-01 15:59 [gentoo-dev] [PATCH 1/5] out-of-source-utils.eclass: New utility eclass Michał Górny
2023-01-01 15:59 ` [gentoo-dev] [PATCH 2/5] multibuild.eclass: Provide run_in_build_dir from out-of-source-utils Michał Górny
2023-01-01 15:59 ` [gentoo-dev] [PATCH 3/5] multilib-build.eclass: Stop providing multibuild.eclass Michał Górny
2023-01-01 15:59 ` [gentoo-dev] [PATCH 4/5] python-r1.eclass: " Michał Górny
2023-01-01 15:59 ` [gentoo-dev] [PATCH 5/5] out-of-source.eclass: Document BUILD_DIR Michał Górny
2023-01-02  9:25 ` [gentoo-dev] [PATCH 1/5] out-of-source-utils.eclass: New utility eclass Ulrich Mueller
2023-01-02 12:24   ` Michał Górny [this message]

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=1cbd5bb92bc498f5cbed7a281ad610a5a36b4986.camel@gentoo.org \
    --to=mgorny@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