sources, that compilation is also done by the client application. The different applications in the image above are: • The Conan client: this is a console/terminal command line application, containing the previous section, we fetched the sources of our library from an external repository. It is a typical workflow for packaging third party libraries. There are two different ways to fetch the sources from an be built. If we know that changes in the channel never imply a source code change, as set in our workflow/lifecycle, we could write: def package_id(self): self.info.requires["MyOtherLib"].full_package()

sources, that compilation is also done by the client application. The different applications in the image above are: • The Conan client: this is a console/terminal command line application, containing the previous section, we fetched the sources of our library from an external repository. It is a typical workflow for packaging third party libraries. There are two different ways to fetch the sources from an be built. If we know that changes in the channel never imply a source code change, as set in our workflow/lifecycle, we could write: def package_id(self): self.info.requires["MyOtherLib"].full_package()

sources, that compilation is also done by the client application. The different applications in the image above are: • The Conan client: this is a console/terminal command line application, containing the previous section, we fetched the sources of our library from an external repository. It is a typical workflow for packaging third party libraries. There are two different ways to fetch the sources from an be built. If we know that changes in the channel never imply a source code change, as set in our workflow/lifecycle, we could write: def package_id(self): self.info.requires["MyOtherLib"].full_package()

the client application. 3 Conan Documentation, Release 1.29.2 The different applications in the image above are: • The Conan client: this is a console/terminal command-line application, containing the previous section, we fetched the sources of our library from an external repository. It is a typical workflow for packaging third party libraries. There are two different ways to fetch the sources from an be built. If we know that changes in the channel never imply a source code change, as set in our workflow/lifecycle, we could write: def package_id(self): self.info.requires["my_other_lib"].full_package()

the client application. 3 Conan Documentation, Release 1.30.2 The different applications in the image above are: • The Conan client: this is a console/terminal command-line application, containing the previous section, we fetched the sources of our library from an external repository. It is a typical workflow for packaging third party libraries. There are two different ways to fetch the sources from an be built. If we know that changes in the channel never imply a source code change, as set in our workflow/lifecycle, we could write: def package_id(self): self.info.requires["my_other_lib"].full_package()

the client application. 3 Conan Documentation, Release 1.31.4 The different applications in the image above are: • The Conan client: this is a console/terminal command-line application, containing the previous section, we fetched the sources of our library from an external repository. It is a typical workflow for packaging third party libraries. There are two different ways to fetch the sources from an be built. If we know that changes in the channel never imply a source code change, as set in our workflow/lifecycle, we could write: def package_id(self): self.info.requires["my_other_lib"].full_package()

the client application. 3 Conan Documentation, Release 1.24.1 The different applications in the image above are: • The Conan client: this is a console/terminal command-line application, containing the previous section, we fetched the sources of our library from an external repository. It is a typical workflow for packaging third party libraries. There are two different ways to fetch the sources from an be built. If we know that changes in the channel never imply a source code change, as set in our workflow/lifecycle, we could write: def package_id(self): self.info.requires["my_other_lib"].full_package()

the client application. 3 Conan Documentation, Release 1.25.2 The different applications in the image above are: • The Conan client: this is a console/terminal command-line application, containing the previous section, we fetched the sources of our library from an external repository. It is a typical workflow for packaging third party libraries. There are two different ways to fetch the sources from an be built. If we know that changes in the channel never imply a source code change, as set in our workflow/lifecycle, we could write: def package_id(self): self.info.requires["my_other_lib"].full_package()

the client application. 3 Conan Documentation, Release 1.26.1 The different applications in the image above are: • The Conan client: this is a console/terminal command-line application, containing the previous section, we fetched the sources of our library from an external repository. It is a typical workflow for packaging third party libraries. There are two different ways to fetch the sources from an be built. If we know that changes in the channel never imply a source code change, as set in our workflow/lifecycle, we could write: def package_id(self): self.info.requires["my_other_lib"].full_package()

sources, that compilation is also done by the client application. The different applications in the image above are: • The Conan client: this is a console/terminal command line application, containing the previous section, we fetched the sources of our library from an external repository. It is a typical workflow for packaging third party libraries. There are two different ways to fetch the sources from an be built. If we know that changes in the channel never imply a source code change, as set in our workflow/lifecycle, we could write: def package_id(self): self.info.requires["MyOtherLib"].full_package()