list of references, as a string, or a yaml list (abbreviated or full as yaml items). All the root nodes will be in the same dependency graph, leading to conflicts if they depend on different versions of operating systems. If PkgD defines a normal requirement to PkgA, then, it will be introducing that edge in the graph, forcing PkgA to be used always, in all operating systems. For this purpose the override directly defined in the command line. • It encodes a graph, not just a list of versions, as different nodes in the graph might be using different versions too. • The options values at each package. As downstream

list of references, as a string, or a yaml list (abbreviated or full as yaml items). All the root nodes will be in the same dependency graph, leading to conflicts if they depend on different versions of operating systems. If PkgD defines a normal requirement to PkgA, then, it will be introducing that edge in the graph, forcing PkgA to be used always, in all operating systems. For this purpose the override directly defined in the command line. • It encodes a graph, not just a list of versions, as different nodes in the graph might be using different versions too. • The options values at each package. As downstream

list of references, as a string, or a yaml list (abbreviated or full as yaml items). All the root nodes will be in the same dependency graph, leading to conflicts if they depend on different versions of operating systems. If PkgD defines a normal requirement to PkgA, then, it will be introducing that edge in the graph, forcing PkgA to be used always, in all operating systems. For this purpose the override directly defined in the command line. • It encodes a graph, not just a list of versions, as different nodes in the graph might be using different versions too. • The options values at each package. As downstream

list of references, as a string, or a yaml list (abbreviated or full as yaml items). All the root nodes will be in the same dependency graph, leading to conflicts if they depend on different versions of operating systems. If PkgD defines a normal requirement to PkgA, then, it will be introducing that edge in the graph, forcing PkgA to be used always, in all operating systems. For this purpose the override directly defined in the command line. • It encodes a graph, not just a list of versions, as different nodes in the graph might be using different versions too. • The options values at each package. As downstream

list of references, as a string, or a yaml list (abbreviated or full as yaml items). All the root nodes will be in the same dependency graph, leading to conflicts if they depend on different versions of operating systems. If PkgD defines a normal requirement to PkgA, then, it will be introducing that edge in the graph, forcing PkgA to be used always, in all operating systems. For this purpose the override directly defined in the command line. • It encodes a graph, not just a list of versions, as different nodes in the graph might be using different versions too. • The options values at each package. As downstream

list of references, as a string, or a yaml list (abbreviated or full as yaml items). All the root nodes will be in the same dependency graph, leading to conflicts if they depend on different versions of operating systems. If pkgd defines a normal requirement to pkga, then, it will be introducing that edge in the graph, forcing pkga to be used always, in all operating systems. For this purpose the override directly defined in the command line. • It encodes a graph, not just a list of versions, as different nodes in the graph might be using different versions too. • The options values at each package. As downstream

list of references, as a string, or a yaml list (abbreviated or full as yaml items). All the root nodes will be in the same dependency graph, leading to conflicts if they depend on different versions of operating systems. If PkgD defines a normal requirement to PkgA, then, it will be introducing that edge in the graph, forcing PkgA to be used always, in all operating systems. For this purpose the override directly defined in the command line. • It encodes a graph, not just a list of versions, as different nodes in the graph might be using different versions too. • The options values at each package. As downstream

list of references, as a string, or a yaml list (abbreviated or full as yaml items). All the root nodes will be in the same dependency graph, leading to conflicts if they depend on different versions of operating systems. If pkgd defines a normal requirement to pkga, then, it will be introducing that edge in the graph, forcing pkga to be used always, in all operating systems. For this purpose the override directly defined in the command line. • It encodes a graph, not just a list of versions, as different nodes in the graph might be using different versions too. • The options values at each package. As downstream

list of references, as a string, or a yaml list (abbreviated or full as yaml items). All the root nodes will be in the same dependency graph, leading to conflicts if they depend on different versions of operating systems. If pkgd defines a normal requirement to pkga, then, it will be introducing that edge in the graph, forcing pkga to be used always, in all operating systems. For this purpose the override directly defined in the command line. • It encodes a graph, not just a list of versions, as different nodes in the graph might be using different versions too. • The options values at each package. As downstream

list of references, as a string, or a yaml list (abbreviated or full as yaml items). All the root nodes will be in the same dependency graph, leading to conflicts if they depend on different versions of operating systems. If PkgD defines a normal requirement to PkgA, then, it will be introducing that edge in the graph, forcing PkgA to be used always, in all operating systems. For this purpose the override directly defined in the command line. • It encodes a graph, not just a list of versions, as different nodes in the graph might be using different versions too. • The options values at each package. As downstream