From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites: dev-php/pear and friends
Date: Wed, 12 Jun 2024 06:30:35 -0400 [thread overview]
Message-ID: <717220cc8f84e84e816197c655c15a6f2f610328.camel@gentoo.org> (raw)
In-Reply-To: <b7bfa240-a1a1-46bf-be41-04f4d938b5a4@gentoo.org>
On Wed, 2024-06-12 at 08:57 +0300, Viorel Munteanu wrote:
>
> I had to bump to EAPI 8 and unmask dev-php/pear, because it's used by
> the eclass. This makes the thread subject a bit wrong, but I won't
> change it.
Thanks, I think once most of the PEAR packages are removed, we'll be
very close to removing the eclass and dev-php/pear, too. No one is
using "pear" as a package manager these days, so aside from two lines
in src_install(), the eclass phase functions are junk. And dev-php/pear
does not actually do anything except pull in dev-php/PEAR-PEAR (which
itself can be greatly simplified if we don't care about "pear").
> About the roundcube dependencies: dev-php/PEAR-Net_IDNA2 is still EAPI 6
> and with no maintainer, and dev-php/PEAR-Net_Socket is also EAPI 6,
> unmaintained, and unmaintained upstream. I'm asking the roundcube
> maintainers if they want to bump them or keep them bundled.
These two didn't have new versions upstream and are stable, so I
skipped them to avoid annoying the arch teams with an -r1 stablereq.
I'm using them (unbundled) for my roundcube installation though so if
that's a deal-breaker, I can bump those too.
prev parent reply other threads:[~2024-06-12 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 4:11 [gentoo-dev] Last rites: dev-php/pear and friends Viorel Munteanu
2024-06-11 11:54 ` Michael Orlitzky
2024-06-11 11:56 ` Arthur Zamarin
2024-06-11 19:48 ` Michael Orlitzky
2024-06-12 5:57 ` Viorel Munteanu
2024-06-12 10:30 ` Michael Orlitzky [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=717220cc8f84e84e816197c655c15a6f2f610328.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