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
Cc: gentoo-dev-announce@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites: dev-php/pear and friends
Date: Tue, 11 Jun 2024 07:54:00 -0400	[thread overview]
Message-ID: <Zmg62NXHklYmJvmP@stitch> (raw)
In-Reply-To: <5c97ac0a-76fe-4054-96b7-5e171579be96@gentoo.org>

On 2024-06-11 07:11:06, Viorel Munteanu wrote:
> 
> # Viorel Munteanu <ceamac@gentoo.org> (2024-06-11)
> # dev-php/pear, dev-php/PEAR-* and their reverse dependencies: mask for 
> removal
> # in 30 days.
> # They are all unmaintained, most of the ebuilds are still EAPI 6, and 
> together
> # they have around 40 bugs.
> # Removal: 2024-07-11.  Bug #933998.
> ...

Some of these should be saved:

 * app-admin/drush is the last version of drush that works with
   Drupal-7.x (still supported upstream) and doesn't bundle a thousand
   dependencies. I've been patching it to avoid warnings with newer
   versions of PHP.

 * dev-php/PEAR-{Auth_SASL,Crypt_GPG,Mail_Mime,Net_IDNA2,Net_Sieve,
                 Net_SMTP,Net_Socket,PEAR}
   are all used by Roundcube. Our ebuilds for mail-client/roundcube
   bundle them right now, but they can be unbundled (just rm -r
   the bundled copies). Afterwards these will have revdeps again.

That subset should be relatively bug-free -- one of the authors of
Roundcube maintains the PEAR packages that it needs. The rest are
indeed obsolete AFAIK though.



  reply	other threads:[~2024-06-11 11:54 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 [this message]
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

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=Zmg62NXHklYmJvmP@stitch \
    --to=mjo@gentoo.org \
    --cc=gentoo-dev-announce@lists.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