Deprecate the PEAR channel #657

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

Projects

None yet

6 participants

@mrook
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

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

@marabesi

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

@drupol
Contributor
drupol commented Jan 30, 2017

I would deprecate the pear channel.

@mrook
Member
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

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
Member
mrook commented Jan 30, 2017

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

@Ocramius

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
Member
mrook commented Jan 30, 2017

Which is precisely what I suggested ;-)

@Ocramius

๐Ÿ‘

@kenguest
Contributor

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
Member
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
Member
mpdude commented Jan 31, 2017 edited

๐Ÿ‘ for new releases via Composer only but keeping a "frozen" PEAR channel.

BTW, any news on the 3.x schedule?

@mrook
Member
mrook commented Jan 31, 2017

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

@mrook
Member
mrook commented Jan 31, 2017

The PEAR channel has been deprecated.

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