[email protected] has been disabled because it is deprecated upstream!

[leqq00]

[email protected] has been disabled because it is deprecated upstream!

这个是什么情况？ 无法安装 老版本的PHP吗

[SMillerDev]

Yes, see https://www.php.net/eol.php

[MuneebRabaney]

And on a MONDAY - Boo hooo!

I feel both ends, however, @SMillerDev - douche move man, people install the entire universe with Node. I mean let's face it, a language is only as safe as the hacker sitting, feeding instructions to the machine.

I have to admit, Yes we want up-to-date software, however, we update the core i.e "PHP" and all of our other packages break. I'd rather have the vulnerability and go in for a fix myself rather than 15 other packages that now broke because of something you just decided to take away.

If you want the community to respect you and this "Personal Home Page" language, you have to show care for others not just be all arrogant and like "Oh well tough titties, It's not my problem! Go make your own tap you, you, youuuuuu PHP 7 wanting a-hole"! Heck if my nose wasn't shoved up NodeJS's and typescript butt Id have opted to maintain this project so that the world can live to see another day of our good ol' friend who they love to hate, Mr PHP 7. I mean it's not like I'm asking for 5 or 4! Sigh

I'm done, anger out. Love you all - now back to find a workaround, Thanks for the eeeerrrrrrr, Therapy?
:)

[SMillerDev]

I'd rather have the vulnerability and go in for a fix myself rather than 15 other packages that now broke because of something you just decided to take away.

If you want to manage it yourself, maybe using a package manager to manage your packages is the wrong approach for you.

Homebrew has clearly defined rules about what is supported, if you don't like those there are multiple ways to override them. If you don't like how Homebrew does things and you don't want to do it yourself I suggest this

[SMillerDev]

It's relevant because it's by the project lead of homebrew, therefore reinforcing my position that if you don't want to maintain something, homebrew doesn't have to either because it's license literally says it doesn't.

[SMillerDev]

The maintainers provide no assurances that the software will ever work for any user or use case (even documented ones)

Here you go, there was no assurance that the software would work and you got lucky that it did until it didn't.

The maintainers are never liable for any problems caused by any use of the software (including damages that require you to pay for repairs)

Hey look, you used Homebrew and it caused the problem that you can't install a version of PHP that PHP no longer supports. Homebrew is not liable for that.

We only ask that Homebrew does not remove important, functional, working, stable packages.

If you want to pin your software stack to a specific version, Homebrew (or any rolling release) is not the tool I'd recommend using. Docker does this way better.

We can argue what it means to be a maintainer for an open source project for a while, but in the end the simple truth is this:

• Homebrew has rules about versions, we followed them here and nothing about that will change.

[MuneebRabaney]

ok; ok; ok Guys 😓, Yes @SMillerDev I agree with you; I'll take a knee on this one as I was wrong. I appreciate what You and other maintainers are doing to keep things going with great GIRTH, so be a fella and please accept my apologies as that rant was out of line. sigh. I need a yellow rubber duckie for my rants, I was a bit ticked off this morning.

We all have those crap Mondays where you worked all weekend trying to make something awesome; and then; there's this that one annoying thing you always use to be able to do with ease - however, now, you can't, and that's all she wrote...

(i.e the switching between PHP versions using homebrew), now you have to use brain power to compute another way. I love homebrew and have been using it for a while, in my opinion, It's the best, super easy and simple to use. Also thanks for the blog links and helpful comments. I managed to fix my issue and ship my code, easy peasy no stress; no; no; no :). And on the plus;

I now have a way forward should I ever be in a similar situation with other software. If there's a way I can contribute I'll submit a PR.

You're doing what's best for us and that sits well in my books
Kudos.

[jjonline]

monterey12.1

Because some old projects still need php7.2 to be used, is there an alternative installation method?

[SMillerDev]

You can try people's personal tap, like https://github.com/shivammathur/homebrew-php

[senguttuvang]

I have inherited a project from another team which used 7.2. It isn't advisable to start with 7.3 or 8.0. I need to first run the app as it is, then slowly migrate to the newer version. The new developer can't be held responsible for what is been maintained by the previous developer/team. You may discourage the usage but do not block it. Let the developer decide which version to use based on several other factors (business priorities, backward compatibility for related package, etc).

Yes, I went with the personal tap mentioned. Thank you!

[SMillerDev]

We're not just arbitrarily restricting PHP versions as you seem to imply. https://www.php.net/eol.php has the supported PHP versions and Homebrew/core is simply following the (PHP) projects direction in this. If you want longer support for PHP versions you can always write to the internals mailinglist requesting such support.

[keeev]

You can try people's personal tap, like https://github.com/shivammathur/homebrew-php

thanks, this hint helped me running my Laravel Project again which depended on 7.3 while others were running on 7.4. 🙌🏼

In case anyone is looking for a solution after updating brew and not being able to run php artisan ... and resulting in:

 dyld: Library not loaded: /usr/local/opt/openldap/lib/libldap-2.4.2.dylib
  Referenced from: /usr/local/bin/php
  Reason: image not found

this might be working for you too.

[henrypenny]

I'm glad I don't have to make my own decisions about which php versions I need to do my job.

[carcinocron]

Yeah, I have no idea why homebrew randomly uninstalled php without my consent. It's really fucking annoying. This has been extremely disruptive and anti-user. Normal software would give you a yellow warning message. This is some bullshit I'd expect from windows. It's not brew's job to FORCE USERS to stop developing software on "days old" versions of PHP. Now it's going to take EVEN LONGER for me to upgrade PHP because I had to do this work-around bullshit.

[carlocab]

You're the only one here who claims that has happened to them

Its happening to lots of us.

Please provide reproduction steps.

[eshe-huli]

I was maintaining from 7.1 to 7.4 in my computer after brew upgrade I first lost 7.1 after another I just realize 7.2 is missing so yes you do remove them from my computer without telling me.

[SMillerDev]

That's interesting, how were you maintaining them in your computer? Since brew should not have access to non-brew files.

[odahcam]

@henrypenny @SMillerDev the thing is not providing support is just making no changes to anything, you simply do nothing, that's the easiest thing. Now the moment you delete something you are changing stuff and that's what I can't understand. You simply have no obligation with anyone as I don't in my open source projects either, but I assure you that if I go there and delete some API I don't like and think it's bad that some folks make use, they will be very pissed off. If you just think about what causes less impact: how many hours you spent explaining why you deleted the formula instead of leaving it deprecated with a message that does that already and also gives the users freedom of choice. You do realize that lots of CI jobs makes use of homebrew to install dependecies just broke because of that? I understand it's your decision and you own no one nothing, but it's a very poor decision in my point of view. I can't trust brew official formulas for LTS software I write anymore, but I'm not complaining anymore, I'm jsut giving my opinion which you should have no obligation to care at all too.

[SMillerDev]

the thing is not providing support is just making no changes to anything, you simply do nothing, that's the easiest thing.

Except that would mean that every update to the python or pcre formula for example would recompile and test an old php that is not likely to be compatible. Or, if we block the CI tests it would compile on your own device and break. (Which would lead to users asking for support)

I can't trust brew official formulas for LTS software I write anymore

As a rolling release system that is not a recommended approach to begin with. Brew is pretty transparant in its goal to always strive for the latest version.