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] Packages up for grabs: apache-2.eclass
Date: Wed, 28 Dec 2022 16:20:02 -0500	[thread overview]
Message-ID: <Y6yzAjgYOaKw3bbK@stitch> (raw)
In-Reply-To: <6c1ea8dc5da4daf9d7979808090ecbc2347ee9d7.camel@gentoo.org>

On 2022-12-26 10:11:18, Hans de Graaff wrote:
> 
> It would be great if you could dust these off and post them here so we
> can get these improvements merged. You mention in the bug that you'd
> rather wait for a dedicated maintainer to review them, but I'm (in
> name) that maintainer and I think you probably know these eclasses
> better than I do. With some joint effort we may get things moving here.

I'm trying to avoid becoming the de facto maintainer of the thirty or
so apache modules that I care nothing about. The eclasses I posted to
the bug are a proof-of-concept for www-apache/mpm_itk, but even that
has a workaround allowing it to use EAPI=7 now. I haven't tested them
with any other packages.

Updating apache-module-r1.eclass to EAPI=8 still requires some work,
and then the whole thing needs to be tested by migrating a
representative chunk of apache-module packages to determine if the
idea is feasible as-is, or if the approach needs to be tweaked. Until
then we'd just be wasting reviewers' time.

I may eventually get bored enough to do all that testing, but right
now I have a lot of things that are actually enjoyable and/or make me
money in front of it on my list.


  reply	other threads:[~2022-12-28 21:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-25 12:09 [gentoo-dev] Packages up for grabs: apache-2.eclass David Seifert
2022-12-25 15:40 ` Michael Orlitzky
2022-12-26  9:11   ` Hans de Graaff
2022-12-28 21:20     ` Michael Orlitzky [this message]
2022-12-26  8:43 ` 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=Y6yzAjgYOaKw3bbK@stitch \
    --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