Changed the log4php requirement source from pear to composer/packagist

[staelche]

Use native composer package of log4php (since it is available) instead of using the pear package

[marcelog]

hey, cool :) shouldn't we also update composer.lock in this same pull request?

[staelche]

Mh. Since you checked it in. Yes.

I didn't realize the .lock file since i don't check it in for my projects. That is because the lock file reflects only the actually selected library versions of the projects requirements. You did the statment in your composer.json that every log4php >= 2.1.0 in fine. In the end you lock projects based on PAGI down to version 2.1.0 since they use the lock file for installing the requirements. Then you could have added the log4php lib only in version 2.1.0 to the project (composer.json) and you would not need the lock file anymore.

2 choices and your decision (I'll do the work):

• Remove the lock file and select only version 2.1.0 of log4php in composer.json
• Or update the lock file manually (since the latest stable version is already 2.3.0 and I think you don't want to test/check the new version for compatibility?) A simple composer update would install it.

After writing this only the first option would make sense to me...

Reference/Discussions:

• https://getcomposer.org/doc/02-libraries.md#lock-file
• http://stackoverflow.com/questions/12896780/composer-lock-part-of-the-repository
• The great symfony project didn't check it in, as well.

[marcelog]

Agreed, @staelche, let's go with #1 :)

[marcelog]

thanks man! :) never liked that pear repository there :)

[staelche]

Welcome