4 ms·
As a PHP developer, merging the PHP repository into core will be disastrous for me. I have 27 packages installed for PHP 5.5 - 7.2, and the versioned extensions
by trebor 9y ago
As a PHP developer, merging the PHP repository into core will be disastrous for me. I have 27 packages installed for PHP 5.5 - 7.2, and the versioned extensions will evaporate. So much of my tooling is built around homebrew and the `homebrew/php` tap, that my entire toolchain for development will change.
The last time, Apache was switched from installing/running at the system level to user-based. That broke almost everything on my system for a day while I tried to fix it. Worse, there wasn't a warning prompt before the package upgraded.
I don't have time for things to break down every 6-12 months.
- mikemcquaid 9y agoAny formula that gets removed you can continue to maintain in your own tap (third-party GitHub repository, https://docs.brew.sh/How-to-Create-and-Maintain-a-Tap.html https://docs.brew.sh/How-to-Create-and-Maintain-a-Tap.html). https://github.com/Homebrew/homebrew-php/issues/4721 https://github.com/Homebrew/homebrew-php/issues/4721 explains what needs to be done. If you want to avoid your workflow being disrupted: chip in and help; we're giving you plenty of warning.
- trebor 9y agoI understand that. However, if I had time to contribute to homebrew, I would have by now. I definitely do not have the time to maintain a tap and keep its packages up to date. I'm glad y'all gave enough warning, but that doesn't make me any less frustrated by the decision.
- mikemcquaid 9y agoSure, I understand your frustration. Similarly I hope you can see that it's frustrating for us when we make it very easy for people to help themselves and they don't try to do so because they are too busy. You have a job, we have jobs and most of Homebrew's work happens outside people's jobs.