Jordi Boggiano
|
4b5abaf44f
|
Fixes in PEAR support
|
2011-11-06 20:24:52 +01:00 |
|
Fabien Potencier
|
527c711149
|
Move loader creation to avoid creating it more than once, unified the way packages are loading across repository classes
|
2011-10-29 07:43:26 +02:00 |
|
Jordi Boggiano
|
dcfe310cff
|
Fix PEAR repository
|
2011-10-28 00:35:35 +02:00 |
|
everzet
|
9deb10361f
|
second batch of refactoring
|
2011-09-21 00:43:53 +03:00 |
|
everzet
|
5f4d46f7ae
|
repository factoring refactoring
|
2011-09-21 00:39:15 +03:00 |
|
Jordi Boggiano
|
49c3446ac1
|
Make use of new dist properties, refactored ZipDownloader
|
2011-07-06 21:06:52 +02:00 |
|
Jordi Boggiano
|
f272f66324
|
Fixes and improvements to the PEAR implementation
|
2011-06-28 20:42:59 +02:00 |
|
Benjamin Eberlei
|
fa613cad19
|
Rewrite PearRepository to implement PEAR Client/Server protocol itself, taking longer then pear remote-list, but at least showing ALL available versions, making arbitrary dependencies possible.
|
2011-06-28 20:42:50 +02:00 |
|
Benjamin Eberlei
|
8afc2ca694
|
Add support for PEAR repository and downloading, example composer.json would look like {"repositories":{"doctrine": {"pear":"http://pear.doctrine-project.org"},"requires":{"DoctrineORM":"2.0.5"}}. You can use pear repositories this way for now. PEAR packages are not downloaded via pear, only via their .tgz packages in the PEAR repository. Automatically detecting dependencies will require reverse-engineering the PEAR protocol a little bit more, however from looking at a pirum output it looks simple.
|
2011-06-28 20:42:48 +02:00 |