Skip to content
This repository was archived by the owner on Nov 19, 2024. It is now read-only.

Php5670 php55 eol#523

Merged
5 commits merged intomagento:developfrom
magenx:PHP5670-PHP55-EOL
Mar 14, 2016
Merged

Php5670 php55 eol#523
5 commits merged intomagento:developfrom
magenx:PHP5670-PHP55-EOL

Conversation

@magenx
Copy link

@magenx magenx commented Feb 11, 2016

PHP 5.5 EOL .
proper repository configured
PHP 7.0 installation

@ghost ghost self-assigned this Feb 13, 2016
@ghost
Copy link

ghost commented Feb 16, 2016

Thanks for the suggestion; please be patient. It might take a while for me to verify everything, esp. with CentOS 7. We'll keep you updated.

ghost pushed a commit that referenced this pull request Mar 14, 2016
@ghost ghost merged commit 0c20bd7 into magento:develop Mar 14, 2016
@ghost
Copy link

ghost commented Mar 14, 2016

Thanks for your patience. We're finally ready to make this change. Be aware that we're going to change your PR quite a bit; namely:

  • Add instructions for Ubuntu
  • Change the example repository to IUS. I've read it's better maintained and might be preferable to webtatic and remi. Also clarified that if you're a developer, the choice of repository might not matter that much.

@ghost
Copy link

ghost commented Mar 14, 2016

Oops, very sorry. I did not notice you were merging to develop, which is a branch we no longer use. Anyway, check out the changes here

@magenx
Copy link
Author

magenx commented Mar 15, 2016

as always magento team is running ahead of a train and making stupid things... is it something that you are specially trained in the company? :)

IUS repository is not better than webtatic, outdated builds, missing packages, not compatible with latest libs. and mostly selectively maintained for their own corporate needs, not for the community and web developer either.

this is why we have stopped using it many years ago.

I think it's time for you to have to get out of the tank and start looking around properly. seriously.

@ghost
Copy link

ghost commented Mar 15, 2016

We take the responsibility of helping our community seriously. When writing any particular instruction, our goal is to provide a reasonable path to achieve a goal, not all possible paths. Particularly regarding third-party software like PHP, there are often no clear-cut answers.

The reason I decided to document IUS rather than webtatic, remi, or others follows:

These repositories are frequently recommended by the community, are usually well maintained, and provide a substantial number of additional packages to CentOS. They are still not associated with CentOS, but are independent.

  • Webtatic is listed under Problem Repositories as follows:

Provides updated packages with later versions of PHP, MySQL, and other packages. IUS or SCL are better alternatives.

  • reddit supports IUS, albeit from one of the maintainers of IUS.
  • A commenter on serverfault says IUS introduces "dependency hell" but there are favorable comments there also.
  • I installed PHP 5.5, 5.6, and 7.0.3 from IUS on CentOS 6 with few issues. Magento installs without issues.
  • We state in our CentOS PHP topic that you have choices: upgrade CentOS, rely on a hosting provider, or choose a repo. We state explicitly that Magento does not recommend a repo, including IUS, but we provide the instructions because it's a reasonable way to do it.

I see you disagree with this choice but then again, you rely on your own experience and wouldn't have used our instructions anyway. Neither myself nor Magento as a whole has anything bad to say about webtatic; our sysadmins say they use it frequently.

In merging your PR, we acknowledge your contribution to our documentation. Thank you and we hope to hear from you again.

@magenx
Copy link
Author

magenx commented Mar 16, 2016

magento 2 have redis and memcached support. how exactly your "sysadmins" configured servers with php 7.0 from IUS and Webtatic to test magento 2??? hmmm

magento-cicd2 pushed a commit that referenced this pull request Dec 14, 2016
This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant