public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [PATCH 1/3] texlive-module.eclass: implicitly set TL_PV if not explicitly set
Date: Thu, 29 Feb 2024 09:34:43 -0500	[thread overview]
Message-ID: <de19a5c3170289e360ae8f536da8fed6dae7bef1.camel@gentoo.org> (raw)
In-Reply-To: <5a0b89a4-a742-4ce3-88ad-63f5b98e346e@gentoo.org>

On Thu, 2024-02-29 at 15:21 +0100, Florian Schmaus wrote:
> > 
> > The eclass only supports EAPIs {7,8,...} so it should suffice to
> > blacklist EAPI=7.
> 
> Fair point, but that would mean to remember to adjust this line once the 
> eclass gets support for EAPI 9.
> 

It should do the right thing automatically when EAPI=9 is added, no? If
the goal of "-gt 8" is to match EAPI=8 and newer, then rejecting (only)
the one EAPI that's older than 8 should be equivalent without involving
a numerical comparison.


  reply	other threads:[~2024-02-29 14:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29 13:38 [gentoo-dev] [PATCH 0/3] *** Three minor changes to texlive-(common|mmodule).elcass *** Florian Schmaus
2024-02-29 13:38 ` [gentoo-dev] [PATCH 1/3] texlive-module.eclass: implicitly set TL_PV if not explicitly set Florian Schmaus
2024-02-29 13:47   ` [gentoo-dev] " Florian Schmaus
2024-02-29 14:08     ` Michael Orlitzky
2024-02-29 14:21       ` Florian Schmaus
2024-02-29 14:34         ` Michael Orlitzky [this message]
2024-02-29 14:36           ` Florian Schmaus
2024-02-29 14:37         ` Michał Górny
2024-02-29 13:38 ` [gentoo-dev] [PATCH 2/3] texlive-common.eclass: check exit status of texmf-update Florian Schmaus
2024-02-29 20:40   ` Ulrich Mueller
2024-03-01  8:47     ` Florian Schmaus
2024-03-01  9:00       ` Ulrich Mueller
2024-02-29 13:38 ` [gentoo-dev] [PATCH 3/3] texlive-common.eclass: Use nonfatal-respecting die for fmtutil-sys Florian Schmaus
2024-02-29 14:38   ` Michał Górny
2024-02-29 20:37     ` Ulrich Mueller

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=de19a5c3170289e360ae8f536da8fed6dae7bef1.camel@gentoo.org \
    --to=mjo@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