Using version ^6.3 for guzzlehttp/guzzle
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
`Using version ^6.3 for guzzlehttp/guzzle
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- symfony/event-dispatcher v4.0.2 requires php ^7.1.3 -> your PHP version (7.0.13) does not satisfy that requirement.
- symfony/event-dispatcher v4.0.2 requires php ^7.1.3 -> your PHP version (7.0.13) does not satisfy that requirement.
- symfony/event-dispatcher v4.0.2 requires php ^7.1.3 -> your PHP version (7.0.13) does not satisfy that requirement.
- Installation request for symfony/event-dispatcher (locked at v4.0.2) -> satisfiable by symfony/event-dispatcher[v4.0.2].
Installation failed, reverting ./composer.json to its original content.
`
hi i would like to install private repo from github instead of packagist, i have setup my composer.json as below
{
"repositories": [
{
"type": "package",
"package": {
"name": "laravel-repo",
"version": "1.1",
"source": {
"url": "https://github.com/jeud/laravel-repo.git",
"type": "git",
"reference": "master"
}
}
}
],
"require": {
"laravel-repo": "1.1"
}
}
it's working but i'm not sure what different between defining type: package
inside repositories
and type: git
without type: package
?
vcs
as a type
Hi. I'm developing a modular application on Composer and have a question regarding dependency inclusions during development.
Currently I have the packages pulled from a VCS.
I have a core module which requires all other modules.
When developing the different modules, I would like to pull in the core module as it implements the user logic.
Though the problem is that when I require-dev the core module, then it tries to automatically install it's dependencies for the modules as well, causing a recursion: e.g help-module > core > help-module...
Does Composer offer any possibilities to pull in a dev dependency without installing the sub-dependencies?
I took laravel/framework as a basis for mine. which yeah basically is the same structure that Symfony follows.
I do see that laravel makes use of the replace
keyword for replacing individual subpackages, but based on the docs I'm not 100% sure if this is a necessary thing for me as well.
Though yes a difference is that laravel supplies a separate laravel/app package which requires the laravel/framework (core) package.
So maybe I will get away by using replace
?
"type": "wordpress-plugin"
but I need it to install into the vendor like a normal "type": "library"
is there anything i can do to overwrite it locally?