This repository has been archived by the owner. It is now read-only.

Homebrew/php deprecation #4721

Closed
MikeMcQuaid opened this Issue Jan 19, 2018 · 11 comments

Comments

Projects
None yet
7 participants
@MikeMcQuaid
Copy link
Member

MikeMcQuaid commented Jan 19, 2018

As announced today this tap will be archived by 31st March 2018. A PR to add a php formula homebrew/core is ongoing.

Help is actively welcomed on any of the above. Let's keep conversation away from disagreement with the decision as that's something that's not going to change, thanks.

@alcaeus

This comment has been minimized.

Copy link
Contributor

alcaeus commented Jan 22, 2018

We will not accept versioned formulae such as php71-mcrypt but any of those listed on https://brew.sh/analytics/install/ will be accepted as part of the default

Forgive my stupid question, I'm not sure I understand: there won't be a php71-mcrypt, but there may be a php-mcrypt, as long as it accepts any installed php package?

In the announcement, you also mentioned the CI workload as a reason for deprecating the tap. Until the tap is officially archived, would it make sense to limit formula updates to supported PHP versions (at this time, 5.6, 7.0, 7.1 and 7.2) in order to reduce CI workload and bottle builds?

@MikeMcQuaid

This comment has been minimized.

Copy link
Member Author

MikeMcQuaid commented Jan 22, 2018

Forgive my stupid question, I'm not sure I understand: there won't be a php71-mcrypt, but there may be a php-mcrypt, as long as it accepts any installed php package?

There won't be either but we'd accept the php or php@7.1 formula installing mcrypt by default.

In the announcement, you also mentioned the CI workload as a reason for deprecating the tap. Until the tap is officially archived, would it make sense to limit formula updates to supported PHP versions (at this time, 5.6, 7.0, 7.1 and 7.2) in order to reduce CI workload and bottle builds?

I don't want to dictate how this tap is run pre-deprecation. That might not be a bad idea but given the tap is going away in a few months I think it's fine as-is until then.

@alcaeus

This comment has been minimized.

Copy link
Contributor

alcaeus commented Jan 22, 2018

There won't be either but we'd accept the php or php@7.1 formula installing mcrypt by default.

Ah, I see, thank you for the explanation! 👍

As for deprecated PHP versions, I've suggested removing unmaintained versions before but it hasn't really gained any traction so it would make sense to keep old versions around if they are not causing big trouble at this time.

@javian

This comment has been minimized.

Copy link
Member

javian commented Jan 22, 2018

Yeah lets not touch the older versions until we migrate everything to core and we will remove (or pass it on to another group of people) them altogeher.

@SMillerDev SMillerDev referenced this issue Jan 23, 2018

Closed

oci8 driver #4725

@MikeMcQuaid MikeMcQuaid referenced this issue Feb 6, 2018

Closed

Feature: support bottles compressed with XZ #3641

5 of 5 tasks complete

TangRufus added a commit to TypistTech/wp-password-argon-two that referenced this issue Feb 28, 2018

@fterrag

This comment has been minimized.

Copy link

fterrag commented Mar 6, 2018

I'm sorry, but I'm a little unclear on how older PHP versions will be supported. If one wanted to install PHP 5.6, would that still be done through this repo (i.e., brew tap homebrew/homebrew-php)?

@javian

This comment has been minimized.

Copy link
Member

javian commented Mar 6, 2018

@fterrag no, the tap would eventually be removed/retired so anything that will be left and supported by the homebrew team will exist in homebrew-core. We are planning on migrating based on current user data which would initially include 7.2, 7.1 and 5.6 .

khs1994 added a commit to khs1994-docker/lnmp that referenced this issue Mar 7, 2018

khs1994 added a commit to khs1994-docker/lnmp that referenced this issue Mar 7, 2018

khs1994 added a commit to khs1994-docker/lnmp that referenced this issue Mar 7, 2018

@Homebrew Homebrew deleted a comment from aierui Mar 9, 2018

@SMillerDev SMillerDev referenced this issue Mar 26, 2018

Closed

php: removed extension 'tidy' #25707

4 of 4 tasks complete
@valentinocossar

This comment has been minimized.

Copy link

valentinocossar commented Mar 29, 2018

There won't be either but we'd accept the php or php@7.1 formula installing mcrypt by default.

Right now to install php with Homwbrew I have to run brew install php72. Why I can't install different versions of php with a suffix like brew install php@7.2? It's a stupid question, but I don't understand why other formulae are using a suffix with the @ to declaring version during the installation process and php doesn't.

Sorry, maybe this is the wrong place where to ask this question, but I noticed the answer quoted above and I decided to ask. Anyway, thank you in advance.

@MikeMcQuaid

This comment has been minimized.

Copy link
Member Author

MikeMcQuaid commented Mar 29, 2018

Right now to install php with Homwbrew I have to run brew install php72. Why I can't install different versions of php with a suffix like brew install php@7.2? It's a stupid question, but I don't understand why other formulae are using a suffix with the @ to declaring version during the installation process and php doesn't.

This will change when the migration is complete.

@MikeLund

This comment has been minimized.

Copy link

MikeLund commented Mar 29, 2018

We are planning on migrating based on current user data which would initially include 7.2, 7.1 and 5.6

Hi, is there somewhere to see the exact numbers? Is 7.0 really that unpopular to be excluded? I'm still a fan of 7.0 and will be sad to see it gone before it's fully EOL.

@MikeMcQuaid

This comment has been minimized.

Copy link
Member Author

MikeMcQuaid commented Mar 29, 2018

Hi, is there somewhere to see the exact numbers?

No, sorry.

I'm still a fan of 7.0 and will be sad to see it gone before it's fully EOL.

You can maintain the formula in your own tap. I suggest forking this tap before that point so you can still use it.

@valentinocossar

This comment has been minimized.

Copy link

valentinocossar commented Mar 29, 2018

This will change when the migration is complete.

Oh super! The completion of the migration is planned by the 31st March 2018? Or the new versioning system to install PHP will change later?

Thank you!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.