output file in json format The result is a list of lists, containing tuples. Each tuple contains 2 elements, the first is a UUID of the node of the graph. It is unique and ensures a way to address exactly being installed/created or a dependency. Same as develop conanfile attribute. – packages: List of elements, representing the binary packages downloaded for the recipe. Normally there will be only 1 element the uploaded recipe. · id: Reference, e.g., “OpenSSL/1.0.2n@conan/stable” ∗ packages: List of elements representing the binary packages found for the recipe. · id: Package ID, e.g., “8018a4df6e7d2b

output file in json format The result is a list of lists, containing tuples. Each tuple contains 2 elements, the first is a UUID of the node of the graph. It is unique and ensures a way to address exactly being installed/created or a dependency. Same as develop conanfile attribute. – packages: List of elements, representing the binary packages downloaded for the recipe. Normally there will be only 1 element the uploaded recipe. · id: Reference, e.g., “OpenSSL/1.0.2n@conan/stable” ∗ packages: List of elements representing the binary packages found for the recipe. · id: Package ID, e.g., “8018a4df6e7d2b

output file in json format The result is a list of lists, containing tuples. Each tuple contains 2 elements, the first is a UUID of the node of the graph. It is unique and ensures a way to address exactly being installed/created or a dependency. Same as develop conanfile attribute. – packages: List of elements, representing the binary packages downloaded for the recipe. Normally there will be only 1 element the uploaded recipe. · id: Reference, e.g., “OpenSSL/1.0.2n@conan/stable” ∗ packages: List of elements representing the binary packages found for the recipe. · id: Package ID, e.g., “8018a4df6e7d2b

output file in json format The result is a list of lists, containing tuples. Each tuple contains 2 elements, the first is a UUID of the node of the graph. It is unique and ensures a way to address exactly being installed/created or a dependency. Same as develop conanfile attribute. – packages: List of elements, representing the binary packages downloaded for the recipe. Normally there will be only 1 element representing the uploaded recipe. · id: Reference, e.g., “openssl/1.0.2u” ∗ packages: List of elements representing the binary packages found for the recipe. · id: Package ID, e.g., “8018a4df6e7d2b

output file in json format The result is a list of lists, containing tuples. Each tuple contains 2 elements, the first is a UUID of the node of the graph. It is unique and ensures a way to address exactly being installed/created or a dependency. Same as develop conanfile attribute. – packages: List of elements, representing the binary packages downloaded for the recipe. Normally there will be only 1 element representing the uploaded recipe. · id: Reference, e.g., “openssl/1.0.2u” ∗ packages: List of elements representing the binary packages found for the recipe. · id: Package ID, e.g., “8018a4df6e7d2b

output file in json format The result is a list of lists, containing tuples. Each tuple contains 2 elements, the first is a UUID of the node of the graph. It is unique and ensures a way to address exactly being installed/created or a dependency. Same as develop conanfile attribute. – packages: List of elements, representing the binary packages downloaded for the recipe. Normally there will be only 1 element representing the uploaded recipe. · id: Reference, e.g., “openssl/1.0.2u” ∗ packages: List of elements representing the binary packages found for the recipe. · id: Package ID, e.g., “8018a4df6e7d2b

output file in json format The result is a list of lists, containing tuples. Each tuple contains 2 elements, the first is a UUID of the node of the graph. It is unique and ensures a way to address exactly being installed/created or a dependency. Same as develop conanfile attribute. – packages: List of elements, representing the binary packages downloaded for the recipe. Normally there will be only 1 element representing the uploaded recipe. · id: Reference, e.g., “openssl/1.0.2u” ∗ packages: List of elements representing the binary packages found for the recipe. · id: Package ID, e.g., “8018a4df6e7d2b

output file in json format The result is a list of lists, containing tuples. Each tuple contains 2 elements, the first is a UUID of the node of the graph. It is unique and ensures a way to address exactly being installed/created or a dependency. Same as develop conanfile attribute. – packages: List of elements, representing the binary packages downloaded for the recipe. Normally there will be only 1 element representing the uploaded recipe. · id: Reference, e.g., “openssl/1.0.2u” ∗ packages: List of elements representing the binary packages found for the recipe. · id: Package ID, e.g., “8018a4df6e7d2b

contains libd/0.1@user/testing, because this package depends on them. Every item in each level has 4 elements: [ref, package_id, context, node-id]. At the moment the only nec- essary one is the first one. The being installed/created or a dependency. Same as develop conanfile attribute. – packages: List of elements, representing the binary packages downloaded for the recipe. Normally there will be only 1 element representing the uploaded recipe. · id: Reference, e.g., “openssl/1.0.2u” ∗ packages: List of elements representing the binary packages found for the recipe. · id: Package ID, e.g., “8018a4df6e7d2b

contains libd/0.1@user/testing, because this package depends on them. Every item in each level has 4 elements: [ref, package_id, context, node-id]. At the moment the only nec- essary one is the first one. The being installed/created or a dependency. Same as develop conanfile attribute. – packages: List of elements, representing the binary packages downloaded for the recipe. Normally there will be only 1 element representing the uploaded recipe. · id: Reference, e.g., “openssl/1.0.2u” ∗ packages: List of elements representing the binary packages found for the recipe. · id: Package ID, e.g., “8018a4df6e7d2b