implode php ports?

[jrmarino]

We've got two megaports so far (tons of subpackages): vlc and now geany-plugins

Another set of candidates for this treatment is php 8.2, 8.3, and 8.4.

I was thinking about implementing this with php 8.5 but I don't see that on the horizon.
Since I already update these ~55 ports per release as a block anyway, it makes a lot of sense.

[kraileth]

I agree, it's probably worth the effort, at least for 8.4 and 8.3 as those are going to stay with us for a while. I can give 8.4 a try.

[jrmarino]

Nah, I'll take a stab at it. There's PHP.mk involved. It's not urgent either

…

On Tue, May 27, 2025, 11:38 kraileth ***@***.***> wrote: I agree, it's probably worth the effort, at least for 8.4 and 8.3 as those are going to stay with us for a while. I can give 8.4 a try. — Reply to this email directly, view it on GitHub <#43 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAISZ5TRQY7DAWMBF565QTT3ASIKBAVCNFSM6AAAAAB6ALIF7WVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMRYGYZTOOA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[jrmarino]

damn, I got really far with some cool stuff and then realized every extension has it's own configuration and build sequence.
Not sure what to do now. Going to save my work in customsource

[jrmarino]

I'm going to put it away for a bit.
it still might be possible to cycle through all the extensions and build in a loop.

[jrmarino]

hmm, looks like the current implementation of "--enable-{extension}" may be wrong, or at least at the top level it's almost always "--with-{extension}" now