I have a Laravel project in which I would like to use my own fork (which combined a pair of pull request requests). The following .json composer works as expected (it extracts the master branch from my repo):
{ "repositories": [ { "type": "vcs", "url": "http://github.com/rmasters/framework" } ], "require": { "php": "5.4.*", "laravel/framework": "dev-master" }, ... "minimum-stability": "dev" }
However, when I add a package that depends on the Illuminate components provided by Laravel (e.g. zizaco/entrust , which requires the same versions as my fork), I get something like this:
In fact, this ends with both my fork and this fork, and the gexge fork has priority in the autoloader.
Is there any way that the dependencies depend on my plug and not try to find another? My fork has the same package name (the .json composer has not been changed) - so I assumed this would work.
Alternatively, is it possible to block certain packages from choosing? (I did not find any documents for this.) Annoyingly, none of the forks seem to have much reason to be in the Pakgastist in the first place, but I think Composer should be able to get around this.
source share