Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128614
Precedence: list
MIME-Version: 1.0
References: <CAOD_yv3eNbN3zvbC+Tq3Fj9wEkN3TEuh4gGE5XPD+z3cPW1NZQ@mail.gmail.com>
 <CAEKnhAHnTE7B_7SxnM9A0Wjnt5z+yLvXfSozm1_-FyqUcLardA@mail.gmail.com>
In-Reply-To: <CAEKnhAHnTE7B_7SxnM9A0Wjnt5z+yLvXfSozm1_-FyqUcLardA@mail.gmail.com>
Reply-To: james@asgrim.com
Date: Wed, 3 Sep 2025 20:20:03 +0100
Message-ID: <CAOD_yv2LQQLn08nLYR1UE4d3cdK+39Qr-JU+RapBHWT=f8nEyA@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] [Discussion] Recommend PIE and deprecate PECL
To: Jakub Zelenka <bukka@php.net>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000a40d02063dea7edf"
From: titcumbjames@gmail.com (James Titcumb)

--000000000000a40d02063dea7edf
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Jakub,

I think the conclusion we came to was that existing PECL extensions may use
the `pecl/` vendor, but new extns should use their own vendor. We can
probably just add that to the PIE docs for clarity, rather than use the RFC
process.

Thanks
James


On Wed, 3 Sept 2025 at 19:54, Jakub Zelenka <bukka@php.net> wrote:

> Hi,
>
> On Sat, Aug 23, 2025 at 9:43=E2=80=AFAM James Titcumb <titcumbjames@gmail=
.com>
> wrote:
>
>> Folks,
>>
>> Presenting the RFC for deprecating PECL and adopting PIE as the
>> recommended extension installer for PHP:
>>
>> https://wiki.php.net/rfc/adopt_pie_deprecate_pecl
>>
>>
> +1 on this in general.
>
> The only thing that might be worth to consider is what to do with
> prefixing of extension repos that we currently have in PHP GH org. Should
> that be also deprecated and should we make clear that we are not going to
> add more of those pecl-* repos and maybe at some point try to move them o=
ut
> of php GH org?
>
> Cheers
>
> Jakub
>

--000000000000a40d02063dea7edf
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div>Jakub,</div><div><br></div><div>I th=
ink the=20
conclusion we came to was that existing PECL extensions may use the=20
`pecl/` vendor,=C2=A0but new extns should use their own vendor. We can=20
probably just add that to the PIE docs for clarity, rather than use the=20
RFC process.</div><div><br></div><div>Thanks</div><div>James</div></div><br=
></div><br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr=
" class=3D"gmail_attr">On Wed, 3 Sept 2025 at 19:54, Jakub Zelenka &lt;<a h=
ref=3D"mailto:bukka@php.net">bukka@php.net</a>&gt; wrote:<br></div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px=
 solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>Hi,</div><b=
r><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, =
Aug 23, 2025 at 9:43=E2=80=AFAM James Titcumb &lt;<a href=3D"mailto:titcumb=
james@gmail.com" target=3D"_blank">titcumbjames@gmail.com</a>&gt; wrote:<br=
></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><=
div>Folks,</div><div><br></div><div>Presenting the RFC for deprecating PECL=
 and adopting PIE as the recommended extension installer for PHP:</div><div=
><br></div><div><a href=3D"https://wiki.php.net/rfc/adopt_pie_deprecate_pec=
l" target=3D"_blank">https://wiki.php.net/rfc/adopt_pie_deprecate_pecl</a><=
/div><div><br></div></div></blockquote><div><br></div><div>+1 on this in ge=
neral.</div><div><br></div><div>The only thing that might be worth to consi=
der is what to do with prefixing of extension repos that we currently have =
in PHP GH org. Should that be also deprecated and should we make clear that=
 we are not going to add more of those pecl-* repos and maybe at some point=
 try to move them out of php GH org?</div><div><br></div><div>Cheers</div><=
div><br></div><div>Jakub</div></div></div>
</blockquote></div>

--000000000000a40d02063dea7edf--