Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate the PEAR channel #657

Closed
mrook opened this issue Jan 29, 2017 · 14 comments
Closed

Deprecate the PEAR channel #657

mrook opened this issue Jan 29, 2017 · 14 comments
Milestone

Comments

@mrook
Copy link
Member

mrook commented Jan 29, 2017

I'm thinking of deprecating the pear.phing.info channel and not release 3.x as a PEAR package.

Right now we're already depending on a few composer packages (symfony/yaml, for example), this poses an issue when generating a PEAR package.

Thoughts?

@Ocramius
Copy link

Do it: even installing PEAR on any machine is a bigger fuss than anything else

@marabesi
Copy link

I agree with @Ocramius, @mrook do have an idea how many installations are made by pear ?

@drupol
Copy link
Contributor

drupol commented Jan 30, 2017

I would deprecate the pear channel.

@mrook
Copy link
Member Author

mrook commented Jan 30, 2017

Our logs show ~7000 downloads from our PEAR channel the past 14 days. Compare that to 140.000 downloads from packagist the past 30 days, roughly 4.5k average daily downloads.

@mrook mrook added this to the 3.0 milestone Jan 30, 2017
@Ocramius
Copy link

Note that PHPUnit also disabled their PEAR channel (eons ago). I fail to see how a deployment/build strategy can work without proper testing as part of it, so they are most probably very old systems that keep crunching and working by sheer luck

@mrook
Copy link
Member Author

mrook commented Jan 30, 2017

@Ocramius yes, I see a fair amount of downloads for older versions in our logs. Probably old systems.

@Ocramius
Copy link

Then you have a very simple solution: stop doing new releases on PEAR, and keep the channel as static contents only, never to be touched again.

@mrook
Copy link
Member Author

mrook commented Jan 30, 2017

Which is precisely what I suggested ;-)

@Ocramius
Copy link

👍

@kenguest
Copy link
Member

Honestly, phpunit no longer pushing updates via a PEAR channel can prove to be a pain in the ass on older machines so I'm not sure I'd call that a good example to follow.

PHP_CodeSniffer still pushes new versions to [the main] PEAR channel, if you're looking for a counter-example.

@mrook
Copy link
Member Author

mrook commented Jan 30, 2017

@kenguest PHP_CodeSniffer requires no external dependencies (other than extensions). At this point we do.

We could do something similar to phpDocumentor (packing the vendor tree inside the PEAR package) but this doesn't seem worth the effort, or useful.

@mpdude
Copy link
Member

mpdude commented Jan 31, 2017

👍 for new releases via Composer only but keeping a "frozen" PEAR channel.

BTW, any news on the 3.x schedule?

@mrook
Copy link
Member Author

mrook commented Jan 31, 2017

@mpdude thanks for your input! No firm schedule yet, we can discuss that on Slack perhaps.

@mrook
Copy link
Member Author

mrook commented Jan 31, 2017

The PEAR channel has been deprecated.

@mrook mrook closed this as completed Jan 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

6 participants