public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: James Le Cuirot <chewi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 1/2] eclass: libtool - Mark compatible EAPIs and introduce BDEPEND
Date: Fri, 7 Sep 2018 15:46:48 +0100	[thread overview]
Message-ID: <20180907154648.55c6150f@red.yakaraplc.local> (raw)
In-Reply-To: <20180907134701.6812-2-grknight@gentoo.org>

On Fri,  7 Sep 2018 09:47:00 -0400
Brian Evans <grknight@gentoo.org> wrote:

> The eltpatch command is run on the build host.
> As such, it needs to be in BDEPEND for EAPI 7.
> 
> Also taking this opportunity to list compatible EAPIs to consider
> future adjustments.
> ---
>  eclass/libtool.eclass | 9 +++++++--
>  1 file changed, 7 insertions(+), 2 deletions(-)
> 
> diff --git a/eclass/libtool.eclass b/eclass/libtool.eclass
> index 2e0f608d342..942bf34aa27 100644
> --- a/eclass/libtool.eclass
> +++ b/eclass/libtool.eclass
> @@ -16,7 +17,11 @@
>  if [[ -z ${_LIBTOOL_ECLASS} ]]; then
>  _LIBTOOL_ECLASS=1
>  
> -DEPEND=">=app-portage/elt-patches-20170422"  
> +case ${EAPI:-0} in
> +	0|1|2|3|4|5|6) DEPEND=">=app-portage/elt-patches-20170422" ;;
> +	7) BDEPEND=">=app-portage/elt-patches-20170422" ;;
> +	*) die "${ECLASS}: EAPI ${EAPI} not supported" ;;
> +esac
>  
>  inherit toolchain-funcs
>  

Why not take the opportunity to bump elt-patches to 20170815?

-- 
James Le Cuirot (chewi)
Gentoo Linux Developer


  reply	other threads:[~2018-09-07 14:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-07 13:46 [gentoo-dev] [PATCH 0/2] Update libtool and autotools with EAPI7 dependencies Brian Evans
2018-09-07 13:47 ` [gentoo-dev] [PATCH 1/2] eclass: libtool - Mark compatible EAPIs and introduce BDEPEND Brian Evans
2018-09-07 14:46   ` James Le Cuirot [this message]
2018-09-07 13:47 ` [gentoo-dev] [PATCH 2/2] eclass: autotools " Brian Evans
2018-09-10 17:11 ` [gentoo-dev] [PATCH 0/2] Update libtool and autotools with EAPI7 dependencies Brian Evans

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=20180907154648.55c6150f@red.yakaraplc.local \
    --to=chewi@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