zlacker

>>TimWol+(OP)
What's the standard way to install php, by using `brew install php` ? Is there a version manager for php itself to have multiple versions of php in the system ?

>>revski+X9
I don't believe there's a specific way to install or manage it. Use the facilities your host OS provides just as you'd do with Ruby, Python or Perl.

As per how to select versions easily, the Symfony project provides a Symfony CLI and one of the features it provides is checking for a `.php-version` file in the current directory and selecting the correct php binary from the PATH accordingly.

I use that when I'm dealing with projects on different versions.

>>adlpz+Tb
> Use the facilities your host OS provides just as you'd do with Ruby, Python or Perl.

Well that's the thing: I don't know anyone who actively develops in Ruby, Python, Perl or Node that uses the OS-packaged runtimes. The system packages and the language-specific package managers live in different universes.

I've seen this situation blamed on both OS packagers or language ecosystems, but now I just think the goals between the two just are fundamentally at odds.

>>mieko+vi
> I've seen this situation blamed on both OS packagers or language ecosystems, but now I just think the goals between the two just are fundamentally at odds.

I hate language-specific package managers. I can see their value to packagers (less work), but they end up arguing with the platform package manager.

It's like there's a load of CS graduates churning out lots of new, better languages; but what's really needed is just one better language. Similarly we have a score of new package managers, creating incompatibilities; so we add some more package managers, to paper over the incompatibilities.

I'm inclined to the view that perhaps there are too many coders in the world, creating compilers and package managers because they can't get a job doing something useful.

https://www.reddit.com/r/linux/comments/nnxng/petition_lenna...