Skip to content

Retire pear.phpunit.de #1229

Closed
sebastianbergmann opened this Issue Apr 20, 2014 · 18 comments
@sebastianbergmann
  • As of sebastianbergmann/phpunit-documentation@ed5264d the PEAR installation method is no longer listed in the documentation for PHPUnit 3.7
  • As of 70b02c6 PHPUnit 3.7 shows a message that the PEAR installation is no longer supported when PHPUnit was installed via PEAR. PHPUnit 3.7.35 is the last release of PHPUnit 3.7 that is made available as a PEAR package.
  • As of sebastianbergmann/phpunit-documentation@05bffa8, PEAR is not advertised as an installation method for PHPUnit 4.0
  • As of 70b02c6 PHPUnit 4.0 shows a message that the PEAR installation is no longer supported when PHPUnit was installed via PEAR. PHPUnit 4.0.17 is the last release of PHPUnit 4.0 that is made available as a PEAR package.
  • No new releases are published on pear.phpunit.de
  • Add a note to the PHPUnit website announcing the shutdown of http://pear.phpunit.de/
  • Add a note to http://pear.phpunit.de/ announcing the shutdown
  • Add a note to the PHPUnit documentation about the shutdown of http://pear.phpunit.de/ and provide help with migration
  • Shut down http://pear.phpunit.de/ (no later than December 31, 2014)
@GrahamCampbell

:+1: Composer all the way. :)

@GrahamCampbell

I think travis-ci still uses pear for phpunit. They will need to move to composer, or phar downloads.

@evert
evert commented Apr 20, 2014

It did not take you very long to be a convert ;)

@jeremeamia

Sounds reasonable to me. Got to think of a similar strategy for some of my projects. Sounds like the end of 2014 marks the end of the Age of PEAR.

@sebastianbergmann

@evert PHAR is the best distribution mechanism, IMHO, for tools. Initially I only offered Composer support because the community demanded it. Now I use Composer to manage PHPUnit's dependencies (during the PHAR build process, for instance).

@mlively
mlively commented Apr 20, 2014

+1 now I don't feel so bad for dumping pear support

@acelaya
acelaya commented Apr 20, 2014

PHAR + Composer should be enough to handle phpunit as a dependency of any project.

@masnun
masnun commented Apr 20, 2014

+1

@yandod
yandod commented Apr 21, 2014

:+1:

@saro0h
saro0h commented Apr 21, 2014

:+1:

@PhilKershaw

Frankly, this is a no-brainer.

@demonkoryu

Thanks.

@thorsten

awesome!

@gcoguiec

Finally :+1:

@beldougie

Big :+1: for the move away from PEAR towards composer!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.