News Feed
Sections




News Archive
Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Nils Adermann:
Composer Replace, Conflict & Forks Explained
February 19, 2014 @ 12:56:41

Nils Adermann has a new post looking at a problem with Composer where it will install a fork of a project rather than the actual project repository. He points out that it is not a security vulnerability in Composer itself, and is usually cause by using the configuration incorrectly.

Recently there has been an increase of cases in which Composer installs a fork of a package instead of the package the user expects. Most frequently these are forks of packages using a "replace" statement in their composer.json. These forks are usually meant for private use only but are still published on Packagist.

The issue stems from the use of "replace" and the publishing of those forked repositories in the Packagist service. "Replace" is meant to define a fork that is still compatible with the original project. The way that Composer handles finding the correct package to install can cause a conflict and the wrong package could end up "winning".

0 comments voice your opinion now!
composer replace fork repository dependency install

Link: http://blog.naderman.de/2014/02/17/replace-conflict-forks-explained

blog comments powered by Disqus

Similar Posts

Phil Bennett: Revisiting: Benchmarking Dependency Injection Containers

Paul Jones' Blog: Sending Mail with Solar

Phantom Reference Blog: Hello NetBeans, this is PHP!

Matthew Weir O'Phinney's Blog: svn:externals (and the Zend Framework)

Matthew Weier O'Phinney's Blog: Cloning the ZF SVN repository in Git


Community Events





Don't see your event here?
Let us know!


interview threedevsandamaybe code community list podcast language laravel series tips release bugfix introduction symfony deployment api zendserver development framework conference

All content copyright, 2014 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework