David Zülke

The issue is that we want to, under normal circumstances, avoid people having `ext-xdebug` running in their production environments. People will specify it in `require`, forget about it, and push....

Will investigate. There are unfortunately minor differences between the "normal" and "interactive" CI runs (interactive TTY, and a wrapping Shell process, mostly) that I think are causing the difference in...

Cool. Yeah, so, having the agent (I don't think the CLI tool is installed by the buildpack, but could be wrong) as a separate package is on my todo for...

> > I can then change the buildpack to detect an agent from that buildpack and provide that package for our platform installs, then the buildpack won't pull in its...

https://github.com/heroku/heroku-buildpack-php/pull/488 addresses most of what we discussed. It now only installs the agent if the user doesn't have the blackfire buildpack set on their app.

Hi Jon, I'll need to look into it, it's been on my list for a while now. The main question is whether it can be done as an alternative PHP...

I don't think we will support it anytime soon. You can build and use the extension yourself without running a forked buildpack; see https://github.com/heroku/heroku-buildpack-php/blob/master/README.md#custom-platform-repositories for instructions.

That no longer works, or at least is no longer advisable, @hacfi. The buildpack can now natively use additional repositories with runtimes or extensions, no forking necessary (except for the...

Maybe @stesie can rework #134 to use the new platform repo infrastructure, and then someone can host the extension in an S3 bucket? :)

Works beautifully, great job @stesie!