We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
how is the dependency graph with "virtual packages" or dependency to capabilities? see https://getcomposer.org/doc/04-schema.md#provide
these relations should result in a relation in the dependency graph.
example: package A depends on psr/log-implementation package B depends on A and depends on cakephp/log (which provides psr/log-implementation)
A
psr/log-implementation
B
cakephp/log
this means , that, effectively, a graph could look like:
[ { ref: 'A', dependsOn: ['psr/log-implementation'], }, { ref: 'B', dependsOn: ['A', 'cakephp/log'], }, { ref: 'psr/log-implementation', dependsOn: ['cakephp/log'], }, { ref: 'cakephp/log' }, ]
The text was updated successfully, but these errors were encountered:
No branches or pull requests
how is the dependency graph with "virtual packages" or dependency to capabilities?
see https://getcomposer.org/doc/04-schema.md#provide
these relations should result in a relation in the dependency graph.
example:
package
A
depends onpsr/log-implementation
package
B
depends onA
and depends oncakephp/log
(which providespsr/log-implementation
)this means , that, effectively, a graph could look like:
The text was updated successfully, but these errors were encountered: