make composer installable through pear

[composer]

make composer installable through pear

[naderman]

I don't think this is a good idea. The goal is to be able to use composer without pear. Composer much like pear is capable of updating itself and we are trying to get away from globally installed system packages, so this seems like a rather bad idea.

[Tyrael]

how would the average user install composer?
if we drop the idea of supporting the installation through pear, then something similar like the go-pear.phar comes to mind (#6 ?).
imo we should make the installation as easy as we can.

[naderman]

Composer should be deliverable and runnable as a phar file. There is no need for it to even be unpackaged. Unlike PEAR, composer is not installed system-wide.

[Tyrael]

so you just download the phar file then. I see.
btw. you mention this the second time: you do know that pear can be installed both system wide and locally, and you can have multiple installation for which you can pass the config file path to the -c argument.

[naderman]

I'm aware that's a possibility, but it's not how most people use pear.

[xaav]

I was hoping to use composer as a plugin manager for one of my web applications.

[naderman]

I don't see how that has anything to with distributing it as a phar file?

[xaav]

It doesn't. But neither does downloading composer from pear.

[Seldaek]

PHAR should be an option for most users, but in Symfony or Typo3 for example that would use composer to handle their plugin, they could bundle it with their distribution one way or another, then its distribution is a non-issue. Anyway yes, a PEAR channel is not really necessary at this point, if it ever becomes relevant we can re-discuss.