You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When Conan checks if a package for a given configuration is available in a remote, it sends just the package ID. It would be very useful to send the information used to compute that hash:
We can send all the configuration: package ID computation is reproducible (needed? desired?)
We can send only the information taken into account to compute the package ID (~conaninfo.txt)
The text was updated successfully, but these errors were encountered:
I've been having a look at it and it can be very challenging to pass the information about the configuration to the place where the calls to the remote are being done. I would say we need first to store the actual configuration for a package (settings, options, requirements,...) in the node object to have it available here
I've been having a look at it and it can be very challenging to pass the information about the configuration to the place where the calls to the remote are being done. I would say we need first to store the actual configuration for a package (settings, options, requirements,...) in the node object to have it available here
That would be accessible in node.conanfile.info object at that point.
When Conan checks if a package for a given configuration is available in a remote, it sends just the package ID. It would be very useful to send the information used to compute that hash:
conaninfo.txt
)The text was updated successfully, but these errors were encountered: