Re: [PECL-DEV] Two questions regarding PHP extensions: include/require + PIE
[email protected] (James Titcumb) Tue, 17 Dec 2024 11:50:13 +0000
| Newsgroups | php.pecl.dev |
|---|---|
| Message-ID | <CAOD_yv3JYE=fA_T0uDf7M9wTgY9_9HbsBuDM94VP=kGc_7Spog@mail.gmail.com> |
--00000000000005cae2062975e77a Content-Type: text/plain; charset="UTF-8" Hi Elmar, On Mon, 16 Dec 2024 at 20:56, Elmar Klausmeier <[email protected]> wrote: > > 2. What are the plans to include the current PECL libs in PIE (PHP > Installer for Extensions)? Is every PECL maintainer supposed to include his > extension separately as a separate vendor? > > Regarding question 2, in short, yes, extensions should belong in their own relevant vendor namespace. The current consensus is that existing extensions who are already hosted on the PHP GitHub organisation are okay to use `pecl/*` vendor initially. The ultimate goal however, is that there should be no `pecl/*` vendors. This is just a general goal, we don't have a roadmap at the moment for anything :) Some discussion around this just happened in https://github.com/composer/packagist/issues/1496 - hope this helps provide some context! Thanks James (note, sorry for re-post, seems I wasn't subscribed to the list) --00000000000005cae2062975e77a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div>Hi Elmar,</div></di= v><br><div class=3D"gmail_quote"><span class=3D"gmail-im"><div dir=3D"ltr" = class=3D"gmail_attr">On Mon, 16 Dec 2024 at 20:56, Elmar Klausmeier <<a = href=3D"mailto:[email protected]" target=3D"_blank">elmar.klausmei= [email protected]</a>> wrote:<br></div><blockquote class=3D"gmail_quote" styl= e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin= g-left:1ex"><div dir=3D"ltr"><br><div>2. What are the plans to include the current PECL libs in PIE (PHP=20 Installer for Extensions)? Is every PECL maintainer supposed to include=20 his extension separately as a separate vendor?</div><div><br></div></div></= blockquote></span><div><div><br></div><div>Regarding question 2, in short, yes, extensions should belong in their own=20 relevant vendor namespace. The current consensus is that=20 existing extensions who are already hosted on the PHP GitHub=20 organisation are okay to use `pecl/*` vendor initially. The ultimate=20 goal however, is that there should be no `pecl/*` vendors. This is just a general goal, we don't have a roadmap at the moment for anything :)</d= iv><div><br></div><div>Some discussion around this just happened in <a href= =3D"https://github.com/composer/packagist/issues/1496" target=3D"_blank">ht= tps://github.com/composer/packagist/issues/1496</a> - hope this helps provi= de some context!</div><div><br></div><div>Thanks</div><div>James</div><div>= <br></div><div>(note, sorry for re-post, seems I wasn't subscribed to t= he list)<br></div></div></div></div></div> --00000000000005cae2062975e77a--